Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

error acquiring token when multiple AD users are signed in #4

Open
austincrft opened this issue Apr 20, 2023 · 0 comments
Open

error acquiring token when multiple AD users are signed in #4

austincrft opened this issue Apr 20, 2023 · 0 comments

Comments

@austincrft
Copy link

It looks like there is a known issue with multiple AD accounts logged in. Here is a quote from the MSAL docs

Known-Issues

A user has multiple accounts signed into their Social Provider (e.g. Google, Facebook, etc.). This happens because the login_hint is not being passed from the B2C service to the Social Provider to tell the Federated IDP which account you are trying to get a token for. If you open the error url in a new tab and see an account selection screen, this is likely what's happening. This is being actively investigated by the B2C Service team.

Source: https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-core/docs/errors.md#refused-to-display--in-a-frame-because-it-set-x-frame-options-to-deny

For many of our clients, their first interaction with our app is a failed login due to this issue. It's easy enough to train them on signing out of other accounts, but I do not view this as an acceptable long-term workaround. Lots of our clients use multiple accounts

Can I get an ETA on this issue? Or at least a good place to keep track of updates?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant