Using MSAL.js in SPA for Azure B2C Authentication - Popup Problem?

So, I was thinking of using MSAL for authentication against the AZURE B2C identifier provider, but from what I see when looking at the code, MSAL depends on the pop-up windows for logging in. (Please correct me if I am wrong).

My question is that, given that B2C sites are consumer-oriented, is the use of pop-ups extremely discouraged, given that many potential site users may be disconnected? I find it hard to find a good example of how to connect Azure B2C to an angular2 application without pop-ups.

+4
source share
2 answers

You can use loginRedirect () instead of loginPopup (); however, Azure B2C does not yet support user domains for the login page, so your users will be redirected to the https://login.microsoftonline.com option . It isn’t scary if you set up branding with your Azure AD tenant, but there is an error when users can get a 400 error. ( Http 400: header request size is too long when a user subscribes using multi-factor verification )

+2
source

hello.js -. , 100% , . . . angular 2. https://github.com/karthikeyanVK/ng2AzureAdB2C

-1

Source: https://habr.com/ru/post/1683421/


All Articles