localStorage as cache location leads to error in chrome #7496
Labels
b2c
Related to Azure B2C library-specific issues
bug-unconfirmed
A reported bug that needs to be investigated and confirmed
msal-browser
Related to msal-browser package
msal-react
Related to @azure/msal-react
Needs: Attention 👋
Awaiting response from the MSAL.js team
public-client
Issues regarding PublicClientApplications
question
Customer is asking for a clarification, use case or information.
Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.27.0
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
2.0.12
Public or Confidential Client?
Public
Description
I want the login state to be shared between tabs. At the moment I use sessionStorage as the cacheLocation. When I changed that to localStorage the login would not work anymore. The page is just blank and I get these errors in the console:
I could only observe this issue in chrome, while other browsers work just fine.
Error Message
No response
MSAL Logs
No response
Network Trace (Preferrably Fiddler)
MSAL Configuration
Relevant Code Snippets
Full config:
Config consumer:
Reproduction Steps
The app should then throw the errors shown in the above image. The user is not logged in, because not all the tokens were set in localStorage.
Expected Behavior
The user should be logged with the tokens stored in localStorage.
Identity Provider
Azure B2C Basic Policy
Browsers Affected (Select all that apply)
Chrome
Regression
No response
The text was updated successfully, but these errors were encountered: