Forum Discussion
Robert Styles
Jul 12, 2017Copper Contributor
Surface Hub Sign on with Okta - fail
We are using Okta for sign in to our environment. We've just gotten our first Surface Hub and it's all configured and updated to current 1703 version. The problem is that when we try to have a user sign on we hit Okta and it sits and spins. Fortunately the account I set up as the resource acount is using domain.onmicrosoft.com so that account atleast works. My initial outreach to Okta is that Surface Hub is not supported. Further testing with my normal Win10 PC also flops on trying to sign on to any of the Office Mobile apps, this is actually the first time I tried it since we've not had a need to use the mobile apps in our environment (everyone's got the full suite installed). If anyone out there is an Okta user and knows if there is a fix / work around I would sure appreciate knowing how to get past this.
10 Replies
Sort By
- David PhillipsSteel Contributor
It's probably best to troubleshoot with a Win 10 PC with the Office Suite and SfB installed. Once you get that working, Surface Hub should work as well.
- Jon CalutanCopper ContributorI have a case open with MS Support and they have advise to connect the hub on a mobile hotspot and it worked with Okta. As a workaround, we could connect the hub on a VLAN with external access so that it connects as it did on the mobile hotspot.
- Robert StylesCopper Contributor
Yes, we've discovered that works, I'm wondering if it's something to do with our internal Okta server not set up for HTTPS authentication. I have the same problem with my non domain joind windows 10 pc and the word/excel/ppt apps.
- TheCleanerCopper Contributor
Yes, we ran into the same issue with both the Surface Hub and internal Win10 users.
It's a known issue and easily remedied changing your IWA server(s) to HTTPS/SSL.