AadHttpClient doesn't work in Safari

%3CLINGO-SUB%20id%3D%22lingo-sub-3088791%22%20slang%3D%22en-US%22%3EAadHttpClient%20doesn't%20work%20in%20Safari%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3088791%22%20slang%3D%22en-US%22%3E%3CP%3EWhy%20is%20this%20issue%20not%20being%20talked%20about%20more%20and%20why%20isn't%20it%20a%20top%20priority%20for%20Microsoft%20to%20fix%3F%20It's%20going%20to%20stop%20working%20other%20browsers%20in%20the%20next%20year%20or%20so%2C%20as%20well.%20I%20just%20spent%20months%20building%20a%20SharePoint%20site%20for%20a%20client%20only%20to%20find%20out%20it%20doesn't%20work%20in%20Safari%20on%20desktop%20and%20mobile%20because%20of%20third%20party%20cookie%20blocking.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EMS%20tried%20to%20apply%20a%20fix%20by%20redirecting%20the%20browser%20to%20a%20different%20URL%20for%20authentication%20but%20that%20method%20only%20works%20about%201%20out%20of%2010%20tries%20for%20me%20(maybe%20I%20have%20too%20many%20AadHttpClient%20API%20calls%20on%20the%20page%3F).%2099%25%20of%20the%20time%20when%20I%20try%20to%20view%20my%20site%20in%20Safari%20I%20get%20the%20following%20error%20and%20none%20of%20my%20API%20calls%20to%20the%20database%20return%20any%20data.%20I%20do%20not%20get%20the%20error%20in%20other%20browsers%20when%26nbsp%3Busing%20the%20same%20user%20account%3CEM%3E.%3C%2FEM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%20style%3D%22%20padding-left%20%3A%2030px%3B%20%22%3E%3CSTRONG%3E%3CEM%3EInteractionRequiredAuthError%3A%20Seamless%20single%20sign%20on%20failed%20for%20the%20user.%20This%20can%20happen%20if%20the%20user%20is%20unable%20to%20access%20on%20premises%20AD%20or%20intranet%20zone%20is%20not%20configured%20correctly%3C%2FEM%3E%3C%2FSTRONG%3E%3C%2FP%3E%3CP%20style%3D%22%20padding-left%20%3A%2030px%3B%20%22%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20turn%20off%20third%20party%20cookie%20blocking%20I%20no%20longer%20get%20the%20error.%20Is%20there%20a%20workaround%20or%20are%20we%20stuck%20waiting%20for%20Microsoft%20to%20change%20how%20authentication%20works%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Why is this issue not being talked about more and why isn't it a top priority for Microsoft to fix? It's going to stop working other browsers in the next year or so, as well. I just spent months building a SharePoint site for a client only to find out it doesn't work in Safari on desktop and mobile because of third party cookie blocking. 

 

MS tried to apply a fix by redirecting the browser to a different URL for authentication but that method only works about 1 out of 10 tries for me (maybe I have too many AadHttpClient API calls on the page?). 99% of the time when I try to view my site in Safari I get the following error and none of my API calls to the database return any data. I do not get the error in other browsers when using the same user account.

 

InteractionRequiredAuthError: Seamless single sign on failed for the user. This can happen if the user is unable to access on premises AD or intranet zone is not configured correctly

 

When I turn off third party cookie blocking I no longer get the error. Is there a workaround or are we stuck waiting for Microsoft to change how authentication works?

0 Replies