Using Azure B2C User Flows is it possible to configure clients with SAML protocol support? Or for is required to use Custom Policies?
No, as per the docs. "This feature is available only for custom policies".
Related
In my project, this a fundamental part of project. Windows Hello for Bussiness and MS Authenticator is secure and easily to use, the goal here is enable this in Azure B2C SUSI to increment safety and provide a fast way to SignIn for user.
The point is, has a way to do that in B2C? Replace normal password to a paswordless way authentiation
There is a possibility to achieve Multi factor authentication using Authenticator app. It is documented and a sample is provider here: Azure AD B2C: TOTP multi-factor authentication
With Azure Active Directory (Azure AD) B2C, you can integrate TOTP-based Multi-Factor Authentication so that you can add a second layer of security to sign-up and sign-in experiences in your consumer-facing applications. This requires using custom policy and custom REST API endpoint. If you already created sign-up and sign-in policies, you can still enable Multi-Factor Authentication.
Below is the user auth flow using TOTP:
At this time, MS does not support primary Auth using Authenticator for B2C. You can request this via the Azure AD B2C forum in feedback.azure.com
SMS and Phone verification are the options available as of now.
We have a requirement wherein we need to send SMS using AAD B2C. We are not using AAD B2C pages. We understand that by using custom policies we can use the SMS feature but how to return the control to the application after SMS generation and validation is done by AAD B2C. The UI is rendered by application.
Please help.
AAD B2C does not provide capabilities to use SMS via an API. You must use the AAD B2C pages to perform MFA or Email verification.
Currently, in ACS we use Yahoo as an identity provider. We noticed that Azure B2C doesn't offer Yahoo as a built-in social provider like Azure ACS. Is there a reason for this and will it be added in the near future?
You can create a custom policy. This allows you to integrate with any OpenId Connect provider. It will require a bit of customization, but should be possible since Yahoo supports OpenID Connect.
Here's the steps to get going with custom policies.
Our current application is authenticating users with a SAML IdP. We wish to retain their implementation of SAML and update the application’s configuration with Azure AD B2C, not switch to OAuth2 or OpenID Connect. Does Azure AD B2C currently support receiving authentication requests via SAML? I am unable to find this in the documentation.
Azure B2C does (has for a while) provide SAML connectivity through custom policies in the Identity Experience Framework currently in public preview - https://learn.microsoft.com/en-us/azure/active-directory-b2c/active-directory-b2c-overview-custom
Azure AD B2C does not support integrating with applications / relaying parties via SAML yet.
You can support this ask and keep up to date on its progress by voting for it in the Azure AD B2C feedback forum: (Application) SAML Protocol support.
You can configure Configure SAML Relying party application:
https://github.com/azure-ad-b2c/saml-sp
The full documentation can be found here:
https://github.com/azure-ad-b2c/saml-sp/blob/master/saml-rp-spec.md
NOTE: AS Per July 2019, SAML Relying Party support is available as a preview feature
I successfully implemented Azure Active Directory for user management/authentication/login in a web app, following this example:
Azure Sample AAD with Flask
I decided to try Azure Active Directory B2C because of its integration for the various social apps. However, I could not get the flask app to work using OAuth 2.0, since Azure AD B2C does not seem to be compatible with OAuth 2.0. I found some documentation that states Azure AD B2C requires Open ID Connect.
Could you please confirm whether Azure Active Directory B2C requires Open ID Connect, or whether it works with OAuth 2.0 as well?
Thanks
It is worth to not that Azure Active Directory B2C (AAD B2C) supports both OpenID Connect and OAuth 2.0 in that it uses these two protocols to exchange information and secure tokens. However, AAD B2C "extends" these protocols by introducing Policies to handle the user experience for Sign-up, Sign-in and general account management.
What does this mean? First of, it means that you cannot create your own sign-up/sign-in experience, you are restricted to redirecting the user to the right policy (which you to some extent can customize). You cannot create your own sign-up/-in UI for this and you are restricted to styling/branding the provided web-based UI for this.
So in order to Authenticate using AAD B2C you could follow this guide, it should be easy enough to adapt to Python. You simply redirect the user to the /authorize endpoint of the AAD B2C and then validate the JWT you receive
Azure AD B2C supports both OpenID Connect and OAuth 2.0 as noted in the official reference protocols documentation.
To be able to sign-in users with Azure AD B2C using OAuth 2.0 and Flask, you'll need to adapt the sample to follow the OAuth 2.0 approach used in this sample: An Android application with Azure AD B2C using OAuth. Key things you'll need to adapt:
You'll need to specify the B2C authorization and token endpoints: https://login.microsoftonline.com/tfp/TENANT_NAME/POLICY_NAME/oauth2/v2.0/authorize. Example from Android sample
You'll need to add your application/client ID as a scope. Example from Android sample
You won't be able to call the Graph's /me endpoint for token validation and to get user details. You'll need to validate the token and extract the claims from it yourself (ideally through a good JWT open source library since this isn't trivial, unfortunately I don't know any that I can recommend at this time).
EDIT
I've created a python sample for Azure AD B2C and used python-jose for token validation and claim retrieval. Check it out.
Based on the documentation here, Azure AD B2C supports both OpenID Connect and OAuth 2.0 protocols.
Azure Active Directory (Azure AD) B2C provides identity as a service
for your apps by supporting two industry standard protocols: OpenID
Connect and OAuth 2.0. The service is standards-compliant, but any two
implementations of these protocols can have subtle differences.