Core Library
MSAL.js (@azure/msal-browser)
Wrapper Library
MSAL React (@azure/msal-react)
Public or Confidential Client?
Public
Description
So I am trying to implement embedded sign-in in my next JS app.
It works fine when policy does not have MFA. But in case of MFA, the redirection after entering user credentials, B2C internally redirects to MFA page inside iframe.
The user wants :
- Normal username/password sign-in to stay embedded in the iframe (as it is now)
- Only when B2C redirects to an MFA page (a different URL), that redirect should happen in window.top instead of inside the iframe
The tricky part is that when loginRedirect is called, MSAL navigates the iframe to B2C's sign-in page, and from there B2C itself handles the flow—including redirecting to MFA if needed. So the MFA redirect isn't something our app code controls directly.
IF there is a solution to this , please help me.
Core Library
MSAL.js (@azure/msal-browser)
Wrapper Library
MSAL React (@azure/msal-react)
Public or Confidential Client?
Public
Description
So I am trying to implement embedded sign-in in my next JS app.
It works fine when policy does not have MFA. But in case of MFA, the redirection after entering user credentials, B2C internally redirects to MFA page inside iframe.
The user wants :
The tricky part is that when loginRedirect is called, MSAL navigates the iframe to B2C's sign-in page, and from there B2C itself handles the flow—including redirecting to MFA if needed. So the MFA redirect isn't something our app code controls directly.
IF there is a solution to this , please help me.