Description
Core Library
MSAL.js (@azure/msal-browser)
Core Library Version
3.26.1
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
2.1.1
Public or Confidential Client?
Public
Description
I switched from Azure B2C user policies to Identity Experience Framework using custom policies (based on the starter pack) and noticed that I now received a monitor_window_timeout
error.
Since I couldn't find anything helpful in the troubleshooting I investigated the whole scenaro and found the following:
The authentication request done by the iFrame was running into the MFA orchestration step of the custom policy which made it timeout:
<!-- Phone verification: If MFA is not required, the next three steps (#5-#7) should be removed.
This step checks whether there's a phone number on record, for the user. If found, then the user is challenged to verify it. -->
<OrchestrationStep Order="7" Type="ClaimsExchange">
<Preconditions>
<Precondition Type="ClaimsExist" ExecuteActionsIf="true">
<Value>isActiveMFASession</Value>
<Action>SkipThisOrchestrationStep</Action>
</Precondition>
</Preconditions>
<ClaimsExchanges>
<ClaimsExchange Id="PhoneFactor-Verify" TechnicalProfileReferenceId="PhoneFactor-InputOrVerify" />
</ClaimsExchanges>
</OrchestrationStep>
Not sure if this is intended or not but at least it is not documented.
I simply removed the orchestration step and it worked again but still wanted to highlight this for transparency...
Error Message
monitor_window_timeout
MSAL Logs
No response
Network Trace (Preferrably Fiddler)
- Sent
- Pending
MSAL Configuration
...
Relevant Code Snippets
...
Reproduction Steps
...
Expected Behavior
...
Identity Provider
Azure B2C Custom Policy
Browsers Affected (Select all that apply)
Chrome
Regression
No response