So I was thinking of using MSAL for authentication against the AZURE B2C Identity Provider, but from what I can see by looking at the code, MSAL is dependent on pop up windows for logins. (Please correct me if I'm wrong).
My question is, given that B2C sites are consumer facing, isn't the use of pop up windows highly discouraged, given that many of your potential site users may have pop up disabled? I'm having difficulty finding a good example of how to plug Azure B2C into an angular2 app without pop up windows.
MSAL does not support SAML. It only supports OAuth / OpenID Connect. SAML is devloped by the Security Services Technical Committee of OASIS (Organization for the Advancement of Structured Information Standards) not by Microsoft so this might be the reason SAML is not included in MSAL Library.
Azure Active Directory B2C (Azure AD B2C) is a customer identity access management (CIAM) solution that enables you to sign up and sign in your customers into your apps and APIs. Your customers use their preferred social, enterprise, or local account identities to get single sign-on access to your applications.
The Microsoft Authentication Library for JavaScript (MSAL. js) uses hidden iframe elements to acquire and renew tokens silently in the background.
In MSAL, you can get access tokens for the APIs your app needs to call using the acquireTokenSilent method which makes a silent request(without prompting the user with UI) to Azure AD to obtain an access token.
You can actually use loginRedirect() instead of loginPopup(); however, Azure B2C does not yet support custom domains for the login page, so your users will be redirected to a variant of https://login.microsoftonline.com. This isn't terrible if you setup branding on your Azure AD tenant, but there is a bug where users may get a 400 error. ( http 400: size of header request is too long when signing in user using Multifactor authentication )
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With