The how-to articles below show you how to create the identity provider application, add the identity provider to your tenant, and add the identity provider to your user flow or custom policy. You typically use only one identity provider in your applications, but you have the option to add more.
You can also add identity providers to your custom policies. You can add identity providers that are supported by Azure Active Directory B2C (Azure AD B2C) to your user flows using the Azure portal. After they successfully sign in, they're returned to Azure AD B2C for authentication with your application. Once a user selects an external identity provider, they're redirected to the selected provider's website to complete their sign-in. On the sign-up or sign-in page, Azure AD B2C presents a list of external identity providers the user can choose for sign-in. With external identity provider federation, you can offer your consumers the ability to sign in with their existing social or enterprise accounts, without having to create a new account just for your application. It is default Microsoft Identity library behavior when you sign in from an external resource AbpUser will be saved without password and AbpUserLogin will.
Azure AD B2C supports external identity providers like Facebook, Microsoft account, Google, Twitter, and any identity provider that supports OAuth 1.0, OAuth 2.0, OpenID Connect, and SAML protocols. You can configure Azure AD B2C to allow users to sign in to your application with credentials from external social or enterprise identity providers (IdP).
0 kommentar(er)
