-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Open
Labels
Needs: Attention 👋Awaiting response from the MSAL.js teamAwaiting response from the MSAL.js teamfeature-unconfirmedmsal-angularRelated to @azure/msal-angular packageRelated to @azure/msal-angular packagemsal-browserRelated to msal-browser packageRelated to msal-browser packagepublic-clientIssues regarding PublicClientApplicationsIssues regarding PublicClientApplicationsquestionCustomer is asking for a clarification, use case or information.Customer is asking for a clarification, use case or information.
Description
Core Library
MSAL.js (@azure/msal-browser)
Wrapper Library
MSAL Angular (@azure/msal-angular)
Public or Confidential Client?
Public
Description
If I want to enable SSO across browser tabs, is there an alternative to using localStorage? I’ve read that storing sensitive information like access tokens or ID tokens in localStorage can pose security risks, even though MSAL allows it.
My goal is for a user to log in once and remain authenticated when they open a new tab, but without relying on localStorage. Are there more secure approaches to achieve this?
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Needs: Attention 👋Awaiting response from the MSAL.js teamAwaiting response from the MSAL.js teamfeature-unconfirmedmsal-angularRelated to @azure/msal-angular packageRelated to @azure/msal-angular packagemsal-browserRelated to msal-browser packageRelated to msal-browser packagepublic-clientIssues regarding PublicClientApplicationsIssues regarding PublicClientApplicationsquestionCustomer is asking for a clarification, use case or information.Customer is asking for a clarification, use case or information.