RedirectHandler.initiateAuthRequest forces another login during msal:acquireTokenSuccess after successful login #7416
Labels
b2c
Related to Azure B2C library-specific issues
bug-unconfirmed
A reported bug that needs to be investigated and confirmed
msal-angular
Related to @azure/msal-angular package
msal-browser
Related to msal-browser package
Needs: Author Feedback
Awaiting response from issue author
no-issue-activity
Issue author has not responded in 5 days
public-client
Issues regarding PublicClientApplications
question
Customer is asking for a clarification, use case or information.
Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.0.25
Wrapper Library
MSAL Angular (@azure/msal-angular)
Wrapper Library Version
None
Public or Confidential Client?
Public
Description
When B2C users are logging in for the first time, they are prompted with the desired flow and, apparently, successfully login. They are redirected to the redirectUri. Before the app loads, guard starts issuing acquireTokenSilent for the protected resources defined in the
protectedResourceMap
. After the first token request, Msal reinitiates auth, sending the user back to the login page. If the user navigates to the app URL, it's successfully logged in. Or it may decide to re-enter the login informations for the second time, which also leads to the expected outcome (a successful session).Error Message
Error - Interceptor - acquireTokenSilent rejected with error. Invoking interaction to resolve. (a couple of times)
MSAL Logs
Network Trace (Preferrably Fiddler)
MSAL Configuration
Relevant Code Snippets
Reproduction Steps
Expected Behavior
After 1st successful login, user should not have to login for the second time
Identity Provider
Azure B2C Custom Policy
Browsers Affected (Select all that apply)
Chrome, Firefox, Edge
Regression
No response
The text was updated successfully, but these errors were encountered: