Enable multi user access in silent-flow to be able to use server with different accounts parallel

Library

• msal@1.x.x or @azure/msal@1.x.x
• @azure/msal-browser@2.x.x
• @azure/msal-node@1.x.x
• @azure/msal-react@1.x.x
• @azure/msal-angular@0.x.x
• @azure/msal-angular@1.x.x
• @azure/msal-angular@2.x.x
• @azure/msal-angularjs@1.x.x

Framework

• Angular
• React
• Other

Expected behavior

Multi user access possible.

Identity Provider

• Azure AD
• Azure B2C Basic Policy
• Azure B2C Custom Policy
• ADFS
• Other

Browsers/Environment

• Chrome
• Firefox
• Edge
• Safari
• IE
• Other (Please add browser name here)

Regression

• Did this behavior work before? Version:

Security

• Is this issue security related?

Source

• Internal (Microsoft)
• Customer request

Description

The silent-flow example works perfectly. I can login and logout.

But when I try to login in 2 different browsers with 2 different accounts. Then the old browser will be logged in with the last logged-in account when page was reloaded.

I know that it always takes the last homeAccountId from cache as the code says:

const account = await msalTokenCache.getAccountByHomeId(app.locals.homeAccountId);

My question is now, how to enable multi users? How to rewrite the app.locals? Is there any example?

Otherwise is need to create some custom code for that?

[pkanher617]

@kwoxer If you need to get all of the accounts currently tracked by msal-node, you can use the getAllAccounts API exposed on the token cache. However this does mean that your app has to have some way to choose or identify which account you are using. You could do this by presenting an account selection screen to the user.

app.locals.homeAccountId is set when the response is retrieved from acquireTokenByCode so that is why it is always taking the last homeAccountId.

[github-actions[bot]]

This issue has been closed due to inactivity. If this has not been resolved please open a new issue. Thanks!