3rd Party OAuth (Okta) Teams issue resolution: Delete PreAuth.json

%3CLINGO-SUB%20id%3D%22lingo-sub-2119457%22%20slang%3D%22en-US%22%3E3rd%20Party%20OAuth%20(Okta)%20Teams%20issue%20resolution%3A%20Delete%20PreAuth.json%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2119457%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Community%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20trying%20to%20figure%20out%20why%20deleting%20the%20preauth.json%20file%20from%20appdata%20rooming%20folder%20solves%20the%20MS%20Teams%20loading%20errors.%26nbsp%3B%20%26nbsp%3BSee%20errors%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhile%20Teams%20is%20open%3A%3C%2FP%3E%3CUL%3E%3CLI%3EWe%20ran%20into%20a%20problem.%20Reconnecting...%3CUL%3E%3CLI%3EWe%20weren't%20able%20to%20access%20your%20conversations.%3C%2FLI%3E%3C%2FUL%3E%3C%2FLI%3E%3C%2FUL%3E%3CP%3EAt%20launch%20of%20Teams%20APP%3C%2FP%3E%3CUL%3E%3CLI%3EWe're%20sorry%20--%20we've%20run%20into%20an%20issue.%3C%2FLI%3E%3C%2FUL%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20wondering%20if%20there%20is%20a%20setting%20in%20the%20preauth.json%20file%20that%20could%20resolve%20these%20common%20issues%20with%20Okta%20OAuth.%26nbsp%3B%20I%20made%20a%20copy%20of%20the%20preauth.json%20before%20I%20delete%20and%20the%20newly%20created%20preauth.json%20file%20and%20don't%20see%20any%20difference.%26nbsp%3B%20%26nbsp%3BBut%20removing%20that%20file%20solves%20the%20issues.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20information%20would%20be%20most%20welcomed.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2119457%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EDeveloper%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EMicrosoft%20Teams%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESettings%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2121488%22%20slang%3D%22en-US%22%3ERe%3A%203rd%20Party%20OAuth%20(Okta)%20Teams%20issue%20resolution%3A%20Delete%20PreAuth.json%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2121488%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F961282%22%20target%3D%22_blank%22%3E%40Shazam13%3C%2FA%3E%26nbsp%3B-%20due%20to%20some%20security%20reasons%20teams%20does%20not%20allow%26nbsp%3B%3CSPAN%3Epreauth.json.%20Please%20upvote%20the%20use%20voice.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2120849%22%20slang%3D%22en-US%22%3ERe%3A%203rd%20Party%20OAuth%20(Okta)%20Teams%20issue%20resolution%3A%20Delete%20PreAuth.json%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2120849%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F590590%22%20target%3D%22_blank%22%3E%40Nikitha-MSFT%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20not%20sure%20what%20you%20mean%20by%20%22Teams%20does%20not%20allow%20the%20preauth.json%2C%20as%20teams%20has%20a%20condition...%22%26nbsp%3B%20The%20preauth.json%20file%20is%20automatically%20generated%20when%20Teams%20app%20launches.%26nbsp%3B%20Basically%20I%20have%20to%20delete%20this%20file%20when%20Teams%20will%20not%20load%20properly%20in%20order%20to%20get%20to%20the%20Okta%20OAuth.%26nbsp%3B%20I%20was%20wondering%20why%20this%20is%20a%20common%20issue%20and%20if%20there%20was%20a%20setting%20in%20the%20preauth.json%20file%20that%20could%20eliminate%20these%20issues.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2120006%22%20slang%3D%22en-US%22%3ERe%3A%203rd%20Party%20OAuth%20(Okta)%20Teams%20issue%20resolution%3A%20Delete%20PreAuth.json%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2120006%22%20slang%3D%22en-US%22%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F961282%22%20target%3D%22_blank%22%3E%40Shazam13%3C%2FA%3E%26nbsp%3B-%20Due%20to%20some%20security%20reasons%20Teams%20does%20not%20allow%20the%26nbsp%3B%3CSPAN%3Epreauth.json%2C%20as%20teams%20has%20a%20condition%26nbsp%3B%22meetingAddinMeetingUrlMismatch%22%3A%20true.%20This%20is%20by%20design.%20If%20you%20want%20to%20make%20this%20available%20in%20teams%26nbsp%3B-%20Could%20please%20go%20and%20upvote%20this%20%3CA%20href%3D%22https%3A%2F%2Fmicrosoftteams.uservoice.com%2Fforums%2F555103-public%2Fsuggestions%2F40799599-fix-security-teams-configuration%22%20target%3D%22_self%22%20rel%3D%22noopener%20noreferrer%22%3Euser%20Voice%3C%2FA%3E%3F%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E
New Contributor

Hi Community,

 

I am trying to figure out why deleting the preauth.json file from appdata rooming folder solves the MS Teams loading errors.   See errors:

 

While Teams is open:

  • We ran into a problem. Reconnecting...
    • We weren't able to access your conversations.

At launch of Teams APP

  • We're sorry -- we've run into an issue.

 

I am wondering if there is a setting in the preauth.json file that could resolve these common issues with Okta OAuth.  I made a copy of the preauth.json before I delete and the newly created preauth.json file and don't see any difference.   But removing that file solves the issues.

 

Any information would be most welcomed. 

 

 

 

 

3 Replies

@Shazam13 - Due to some security reasons Teams does not allow the preauth.json, as teams has a condition "meetingAddinMeetingUrlMismatch": true. This is by design. If you want to make this available in teams - Could please go and upvote this user Voice?

@Nikitha-MSFT 

I am not sure what you mean by "Teams does not allow the preauth.json, as teams has a condition..."  The preauth.json file is automatically generated when Teams app launches.  Basically I have to delete this file when Teams will not load properly in order to get to the Okta OAuth.  I was wondering why this is a common issue and if there was a setting in the preauth.json file that could eliminate these issues.

@Shazam13 - due to some security reasons teams does not allow preauth.json. Please upvote the use voice.

www.000webhost.com