Azure B2C: Local or Social discovery using email address
We have implemented a B2C custom policy that allows users to sign in with B2C Local or Social (Entra) accounts. Our login screen has a unified sign-in page that was modeled on the SocialAndLocalAccounts starter pack, so we have the option to sign in with an Entra account, or username/password for local accounts.
Azure B2C: add output claims for local sign in
I have a custom policy running in B2C. Most of our users are local to B2C, but we also have our company’s Entra ID tenant set up as an identity provider via OpenID Connect.
Azure B2C add email to the token after verified it
Hi everyone,
Azure B2C add email to the token after verified it
Hi everyone,
returning the AD objectId instead of the B2C objectId
In our system we’ve added Azure AD Identity Provider to a canned SignInUp user flow and it is working. Now we want to use the Home Realm Discovery custom policy but it is working very differently. (HRD: https://github.com/azure-ad-b2c/samples/blob/master/policies/default-home-realm-discovery/readme.md)
returning the AD objectId instead of the B2C objectId
In our system we’ve added Azure AD Identity Provider to a canned SignInUp user flow and it is working. Now we want to use the Home Realm Discovery custom policy but it is working very differently. (HRD: https://github.com/azure-ad-b2c/samples/blob/master/policies/default-home-realm-discovery/readme.md)
returning the AD objectId instead of the B2C objectId
In our system we’ve added Azure AD Identity Provider to a canned SignInUp user flow and it is working. Now we want to use the Home Realm Discovery custom policy but it is working very differently. (HRD: https://github.com/azure-ad-b2c/samples/blob/master/policies/default-home-realm-discovery/readme.md)
returning the AD objectId instead of the B2C objectId
In our system we’ve added Azure AD Identity Provider to a canned SignInUp user flow and it is working. Now we want to use the Home Realm Discovery custom policy but it is working very differently. (HRD: https://github.com/azure-ad-b2c/samples/blob/master/policies/default-home-realm-discovery/readme.md)
returning the AD objectId instead of the B2C objectId
In our system we’ve added Azure AD Identity Provider to a canned SignInUp user flow and it is working. Now we want to use the Home Realm Discovery custom policy but it is working very differently. (HRD: https://github.com/azure-ad-b2c/samples/blob/master/policies/default-home-realm-discovery/readme.md)
returning the AD objectId instead of the B2C objectId
In our system we’ve added Azure AD Identity Provider to a canned SignInUp user flow and it is working. Now we want to use the Home Realm Discovery custom policy but it is working very differently. (HRD: https://github.com/azure-ad-b2c/samples/blob/master/policies/default-home-realm-discovery/readme.md)