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
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.
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?
The text was updated successfully, but these errors were encountered:
It looks like there is a known issue with multiple AD accounts logged in. Here is a quote from the MSAL docs
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?
The text was updated successfully, but these errors were encountered: