When an application that is run on Microsoft Edge tries to acquire a token for a resource, the application may get stuck in an infinite loop of the acquire token call. Infinite acquire token loops and AADSTS50058 error. ![]() This is usually accompanied by an invalid_state error in the session storage. ![]() When users sign in to the application on Microsoft Edge, they're redirected back from the Microsoft Entra login page and are stuck in an infinite redirect loop resulting in repeated page reloads. Infinite redirect loops and page reloads during authentication. When the session storage is cleared, this state is lost and hence results in broken experiences. MSAL.js saves certain state in the session storage and relies on checking this state during the authentication flows. Specifically, the session storage is cleared in the regular browser navigation, and both the session and local storage are cleared in the InPrivate mode of the browser. In this particular version of Microsoft Edge, when the application is redirected across zones, the session storage and local storage are cleared. The session storage and local storage are partitioned by security zones in the Microsoft Edge browser. The cause for most of these issues is as follows. ![]() While Microsoft Edge works on a resolution, here's a description of the frequently occurring issues and the possible workarounds that can be implemented. We're tracking these and have informed the Microsoft Edge team. We had multiple reports of issues with authentication in IE and Microsoft Edge (since the update of the Microsoft Edge browser version to 40.15063.0.0). In this article Issues due to security zones
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |