Now, let’s figure out why it didn’t work for the first time…(more…)
If you use SAML SSO to log into the Workspace ONE UEM (AirWatch) console, you may see this warning after upgrading to 1904. First – don’t panic! Everything still functions!
Now that we’re calm, let’s find out what it is and how to address it. On the menu today:
- What is this strange warning and why/when is it displayed?
- How to configure the UEM Console SSO in order to make it go away
- If you are missing the objectGUID attribute – how to add it for
- VIDM Connector (direct VIDM integration)
- ACC (AD Basic integration)
With WorkspaceONE deployed, many users begin their day at the main page of the WS1 Portal. Which, if you are using a cloud version, is usually hosted at a URL like <yourname>.vmwareidentity.eu (or com/etc for other regions). Many don’t like this and want something like login.mycorp.com instead. Here’s a short note on how to make it, and make it right!
How to make it …wrong!
Our first thought would be: “Not a problem – I’ll just have a DNS CNAME (alias)!”
login.mycorp.com –> mycorp.vmwareidentity.eu
This will not work. The client traffic WILL be redirected to the IP address of the cloud portal, but the URL in all the HTTP headers will still remain login.mycorp.com. And this is not what WS1 expects. At the minimum you will see this:
How to make it …right!
What we need instead if a proper web redirect (HTTP 301 Moved Permanently code) that will basically tell the browser “go to mycorp.vmwareidentity.eu instead“, including all the necessary HTTP header changes.
One way to do it is to deploy a web server hosting the login.mycorp.com URL and responding with the HTTP 301 Code. But this is complicated and we need a web server. Is there an easier way?
Maybe. Many cloud DNS hosters offer a WR or Web Redirect type of record. Basically, this is exactly the above web server, but they host it for you, and you manage this as just another DNS record type. Here’s how it looks in my CloudDNS console (they did not pay me for this post, but they are the only sensible free DNS provider I could find)
Now if we go to our short login URL we will see a proper login screen and the following network trace in the browser (here I use Chrome Developer Tools). I believe this is pretty self-explanatory. Note that we also don’t need to touch any SSL certs, cookies or anything else. It. Just. Works.
Now you know two ways to make the life of your users easier by providing them with a short login URL for their WorkspaceONE portal. One of those ways actually works! 🙂
What is your opinion, do you use shortened names in general or this is just a fad and waste of time? Write below!