
Description
Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
4.4.0
Wrapper Library
Not Applicable
Wrapper Library Version
2.0.0
Public or Confidential Client?
Public
Description
In your samples documentation, you show a MSAL setup for ChromiumApp.
This does not work. It does not persist. And since it uses a popup, this gets a new local storage or session storage every time it's clicked.
This means none of your authentication state is persisted.
React also doesn't work. You can get it working with with a lot of workarounds, even though there is NO documentation regarding this.
But even then authentication state is not persisting in any way, shape or form. If you have content scripts, popup windows, or anything else, you have to again and again sign in.
The sample is also using a 5 year old version and is completely outdated.
Please show a working (react) typescript sample that ACTUALLY works in a browser extension.
Error Message
none
MSAL Logs
No response
Network Trace (Preferrably Fiddler)
- Sent
- Pending
MSAL Configuration
{ as per documentation }
Relevant Code Snippets
your own samples.
Reproduction Steps
- clone sample
- add settings
- run the auth
- close popup and open again.
- you now have to AGAIN sign in.
Expected Behavior
auth state is persisted.
react library works.
Identity Provider
Entra ID (formerly Azure AD) / MSA
Browsers Affected (Select all that apply)
Chrome
Regression
No response