Issue: Windows 10, Office 2016 OneDrive for Business and ADAL Skip to main content
https://support.okta.com/help/answers?id=906f0000000xzjtia4&refurl=http%3a%2f%2fsupport.okta.com%2fhelp%2fanswers
How satisfied are you with the Okta Help Center?
Thank you for your feedback!
How satisfied are you with the Okta Help Center?
1
2
3
4
5
Very Dissatisfied
Very satisfied
Enter content less than 200 characters.
Ask Search:
Shawn SaucierShawn Saucier 

Issue: Windows 10, Office 2016 OneDrive for Business and ADAL

Followed instructions for enabling ADAL at: https://support.okta.com/help/blogdetail?id=a67F0000000blQFIAY

Note:  I've opened case 00125052 for this, but it's stalled due to Oktane.  Hoping the community can help.

Works great for all except OneDrive for Business
Trying to sync OneDrive for Business to the Office 365 account. Can log in fine to the microsoft office 365 site and access Onedrive for Business that way (no problem). Once you click Sync, the web site opens the OneDrive for Business client and prompts for where to save the library (no problem). Once you click "Sync Now" you get a "We're getting things ready to sync..." message and then are redirected to the OKTA sign on page with a "signing in to Office 365" message (so far so good).

Then you receive a "Script error" popup window.
"An error has occurred in the script on this page." Line: 1 Char: 708 Error: Could not complete the operation due to error 8070000c. URL: https://paragon.okta.com/js/widget/spin.min.js?resourceHash=2ad3480baedcac93aa2bbb81072d3876"
 
I suspect the hash part is different, but I know the error code and rest of the URL are the same even on a different machine. See below for images of what is received. This happens on multiple machines with Windows 10 and Office 365 (Office 2016 version) insatalled.  Appears OK with Windows 7/Office 2016.

Interface for ADAL logins to OneDrive for Business
Shawn SaucierShawn Saucier
I did find a workaround.  It's not a FIX though...

The workaround:  Disable ADAL for Office 2016. That prevents the "modern" authentication which uses the web based authentication. 

Here is the article to reference 
https://support.office.com/en-us/article/Enable-Modern-Authentication-for-Office-2013-on-Windows-devices-7dc1c01a-090f-4971-9677-f1b192d6c910?ui=en-US&rs=en-US&ad=US 

In the section titled: Disable modern authentication on devices 
I adapted the reg key path to the Office\16.0 version and sync was successful. 

I still want to be able to use ADAL so that my users are not prompted for credentials every time they launch an office app that wants to connect to Office 365.
BHFSmor BHFSmorBHFSmor BHFSmor
Hi Shawn - did you ever get a real solution for this? I have the same issue with OD for Biz on my Win10 machine running Office 2013. 
Shawn SaucierShawn Saucier
Unfortunately no.
The ticket is still being escalated in OKTA support, and there hasn't been any traction yet.  :(
Okta AdminOkta Admin
Have you tried the new preview onedrive for business sync client?  Once i was able to download that and install my issue like you were having above went away.  This new preview is a complete redesign from MS.  Give that a try if you havent.
Shawn SaucierShawn Saucier

It looks like the preview is closed. 

Not sure when they plan on releasing it though.

The page says:

 

“Thanks for your interest in the next-generation sync client.

 The waitlist is now closed as we are very close to the production-ready release! Stay tuned for further announcements in the coming weeks.”

 

Eric KarlinskyEric Karlinsky (Okta, Inc.)
Hey Shawn,

Any chance you have the New Okta Sign-In Flows enabled? This could be causing an issue, and if you revert back to the old flows, it could resolve this problem.

Thanks,
Eric
Craig Davis (Admin)Craig Davis (Admin)
Having the same issue.  Assuming this is an Okta issue and we are waiting on Okta to resolve?  I'm in the process of upgrading 900 users to Office 2016 and anitcipate this will generate a lot of calls to the helpdesk.
Craig Davis (Admin)Craig Davis (Admin)
The javascript error I am seeing references: https://calix.okta.com/assets/js/widget/spin.min.2ad3480baedcac93aa2bbb81072d3876.js
Marc JordanMarc Jordan (Okta, Inc.)
Just to close the loop here, this issue was resolved January 2016 (Release 2016.04).

Microsoft's Modern Authentication Preview concluded 5/18 and is now released to General Availability. As a result, Okta supports signing in to all versions of Microsoft clients that support Modern Authentication (as detailed here https://blogs.office.com/2015/11/19/updated-office-365-modern-authentication-public-preview/)

Please get in touch if you encounter Authentication problems signing into your Office Clients or Apps.