You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first user login is fine and the access token is retrieved. However, the second call to acquireTokenSilent (which uses a different loginHint) returns the access token from the first account.
I am not sure whether you support multiple accounts. If so, I believe this is a bug - I would expect the access token returned to respect the login_hint param as well as the scope.
Thanks
Iain
The text was updated successfully, but these errors were encountered:
IainAdamsLabs
changed the title
Does MSAL.js support multiple accounts?
Does MSAL.js support multiple accounts? Using acquireTokenSilent
May 11, 2020
IainAdamsLabs
changed the title
Does MSAL.js support multiple accounts? Using acquireTokenSilent
Does MSAL.js support multiple accounts using acquireTokenSilent?
May 11, 2020
Unfortunately we don't have multiple account support at this time, but we are working on adding this feature soon.
You can switch accounts by calling loginRedirect or loginPopup with your login_hint, but MSAL currently only keeps track of the most recently acquired account.
Library
msal@1.x.x
or@azure/msal@1.x.x
@azure/msal-browser@2.x.x
@azure/msal-angular@0.x.x
@azure/msal-angular@1.x.x
@azure/msal-angularjs@1.x.x
Description
I want my application to support multiple MS accounts at once.
In my application the user logs in outside of MSAL, however, the session is still valid on the Authentication server.
I am following the instructions at https://docs.microsoft.com/en-us/azure/active-directory/develop/msal-js-sso#sso-without-msaljs-login to retrieve an Access Token using
acquireTokenSilent
.The first user login is fine and the access token is retrieved. However, the second call to acquireTokenSilent (which uses a different loginHint) returns the access token from the first account.
I am not sure whether you support multiple accounts. If so, I believe this is a bug - I would expect the access token returned to respect the login_hint param as well as the scope.
Thanks
Iain
The text was updated successfully, but these errors were encountered: