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 s...
TheCleaner
Jan 08, 2018Copper 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.
Steve Parankewich
Jan 24, 2018Copper Contributor
What is the new user experience? Are you double prompted for creds when you sign in? Once with a Windows Auth grey box followed by an OKTA sign in web page?
- TheCleanerJan 27, 2018Copper Contributor
Correct. Double prompted currently. We are migrating all MS/O365/Azure related SSO from Okta to Azure AD this year because of this and other SSO abnormalities in Intune, Outlook, etc. Having Okta in the middle without reason isn't making sense for us for anything MS related.
- Steve ParankewichJan 29, 2018Copper ContributorAcrually 3 times since you have to use your email address, then windows auth and then Okta auth. OKTA continues to tell us that Surface Hub support won't be coming unless the feature request goes high on the request list. They say they aren't popular enough. What they don't realize is very large customers with a small amount of Surface Hubs are leaving because of it. We will be moving off as well.
- Daniel HudsonJan 29, 2018Steel ContributorThis is the best response to OKTA. If they won't help their customers by ensuring their product works with vital infrastructure then move your investment elsewhere. They'll eventually wise up, but by then it'll be too late most likely.
Money speaks louder than anything to companies.