Forum Discussion
Surface Hub Sign on with Okta - fail
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.
Yes, we ran into the same issue with both the Surface Hub and internal Win10 users.
https://support.okta.com/help/Documentation/Knowledge_Article/Troubleshooting_Known_Issues/Cannot-sign-into-an-Office-2016-application-on-Windows-10
It's a known issue and easily remedied changing your IWA server(s) to HTTPS/SSL.
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?
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.
We had to make some registry settings for the Okta authentication to work internally (EnableAdal = 1 ao) I'm trying to find out how to make those settings on the SurfaceHub
There are remote management options if you have an MDM solution, but I don't see anything in there about ADAL. Maybe in the future?
https://docs.microsoft.com/en-us/surface-hub/manage-settings-with-mdm-for-surface-hub
