<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
System Status
Announcements
Announcements
Search
Search
Select Language
Knowledge Base
Knowledge Articles
Support Videos ↗
Documentation
Product Documentation ↗
Developer Documentation ↗
Product Release Notes ↗
Community
Events & Webinars
Okta Ideas ↗
Resources
Product Hub
Customer Success Hub
Product Release Update
Learning
Okta Learning ↗
Get Support
Open a Case
HomeCommunityForum
0D50Z00008C3jfISAROkta Classic EngineOkta Integration NetworkAnswered2024-04-30T09:18:25.000Z2015-11-05T16:35:42.000Z2017-05-09T14:32:38.000Z

wjt35 (wjt35) asked a question.

Edited by varun.kavoori1.5210444522562532E12 September 5, 2018 at 1:19 AM
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.

 

0EMF0000000bqAP
  • 9 answers
  • 3.39K views

  • wjt35 (wjt35)

    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.
    Expand Post

  • j5v7c (j5v7c)

    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.

  • wjt35 (wjt35)

    Unfortunately no.

    The ticket is still being escalated in OKTA support, and there hasn't been any traction yet.  😞

  • j5v7c (j5v7c)

    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.

  • wjt35 (wjt35)

     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.”

     

      

    Expand Post

  • eric.karlinsky1.4147731941881877E12 (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
    Expand Post

  • 2wc4c (2wc4c)

    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.

  • j5v7c (j5v7c)

    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.

    Expand Post
This question is closed.
Loading
Issue: Windows 10, Office 2016 OneDrive for Business and ADAL