1993saurabh / active-directory-b2c-custom-policy-samples

Azure Active Directory B2C custom policy samples

This GitHub repository contains the following Azure Active Directory B2C custom policy samples:

Name	Description
sign_up_sign_in	Sign-up for a local account using an e-mail address and a phone number. The end user is prompted for verification of the e-mail address and the phone number. Sign-in for a local account using an e-mail address or a phone number. If the e-mail address hasn't been verified, then the end user is prompted for verification of the e-mail address. If the phone number hasn't been verified, then the end user is prompted for verification of the phone number.
sign_up_with_hibp	Sign-up for a local account using an e-mail address. The e-mail address and password are checked against Have I Been Pwned (HIBP) for whether they have been disclosed through a data breach. The end user is prompted for verification of the e-mail address.
sign_up_with_keen	Sign-up for a local account using an e-mail address. The end user is prompted for verification of the e-mail address. A registration event about the new user is published to Keen.
sign_up_with_mailgun	Sign-up for a local account using an e-mail address. The end user is prompted for verification of the e-mail address. An e-mail notification about the new user is sent through Mailgun.
sign_up_with_mandrill	Sign-up for a local account using an e-mail address. The end user is prompted for verification of the e-mail address. An e-mail notification about the new user is sent through Mandrill.
sign_up_with_sendgrid	Sign-up for a local account using an e-mail address. The end user is prompted for verification of the e-mail address. An e-mail notification about the new user is sent through SendGrid.
sign_up_without_verification	Sign-up for a local account using an e-mail address and a phone number. The end user is not prompted for verification of the e-mail address or the phone number.
sign_in_with_verification	Sign-in for a local account using an e-mail address or a phone number. If the e-mail address hasn't been verified, then the end user is prompted for verification of the e-mail address. If the phone number hasn't been verified, then the end user is prompted for verification of the phone number.
email_sign_up_any_sign_in	Sign-up for a local account using an e-mail address. The end user is prompted for verification of the e-mail address. A phone number can be linked to the local account using the phone_linking policy. Sign-in for a local account using an e-mail address or a phone number. If the e-mail address hasn't been verified, then the end user is prompted for verification of the e-mail address. If the phone number hasn't been verified, then the end user is prompted for verification of the phone number.
phone_sign_up_any_sign_in	Sign-up for a local account using a phone number. The end user is prompted for verification of the phone number. An e-mail address can be linked to the local account using the email_linking policy. Sign-in for a local account using an e-mail address or a phone number. If the e-mail address hasn't been verified, then the end user is prompted for verification of the e-mail address. If the phone number hasn't been verified, then the end user is prompted for verification of the phone number.
email_linking	Linking of an e-mail address to a local account that has been registered using a phone number. The end user is prompted for verification of the e-mail address.
phone_linking	Linking of a phone number to a local account that has been registered using an e-mail address. The end user is prompted for verification of the phone number.

Prerequisites

If you don't already have one, then you must create an Azure AD B2C tenant that is linked to your Azure subscription.

Prepare the Azure AD B2C tenant for the custom policies

Prepare your Azure AD B2C tenant by creating the token signing and encryption keys and creating the Identity Experience Framework applications.

Create the custom attributes for the custom policies

Create a custom attribute for each of the following attributes:

Name	Data Type	Description
EmailVerified	Boolean	A value indicating the end-user's e-mail address has been verified.
PhoneVerified	Boolean	A value indicating the end-user's phone number has been verified.

Clone or download the custom policies

From the command line:

git clone https://github.com/chrispadgettlivecom/active-directory-b2c-custom-policy-samples.git

Configure the custom policies

The custom policies can be configured for your Azure AD B2C tenant by creating a configuration file and then generating the XML files to be uploaded to your Azure AD B2C tenant.

Create a configuration file

Add a local.json file or edit the default.json file in the Policies\config directory with the configuration settings for your Azure AD B2C tenant.

{
  "iefAuthenticationApplication": {
    "clientId": "<IdentityExperienceFrameworkApplicationAppId"
  },
  "iefAuthenticationProxyApplication": {
    "clientId": "ProxyIdentityExperienceFrameworkApplicationAppId"
  },
  "iefExtensionApplication": {
    "id": "B2CExtensionsApplicationObjectId",
    "clientId": "B2CExtensionsApplicationObjectId"
  },
  "tenant": {
    "name": "your-tenant-name.onmicrosoft.com"
  }
}

Generate the XML files

Run the build task in the Policies directory to generate the XML files in the Policies\dist directory.

gulp build

Upload the custom policies

Upload the XML files in the following order in your Azure AD B2C tenant:

1. B2C_1A_base.xml
2. B2C_1A_extension.xml
3. B2C_1A_email_linking.xml
4. B2C_1A_email_sign_up_any_sign_in.xml
5. B2C_1A_phone_linking.xml
6. B2C_1A_phone_sign_up_any_sign_in.xml
7. B2C_1A_sign_in_with_verification.xml
8. B2C_1A_sign_up_sign_in.xml
9. B2C_1A_sign_up_with_hibp.xml
10. B2C_1A_sign_up_with_keen.xml
11. B2C_1A_sign_up_with_mailgun.xml
12. B2C_1A_sign_up_with_mandrill.xml
13. B2C_1A_sign_up_with_sendgrid.xml
14. B2C_1A_sign_up_without_verification.xml

Test the custom policies

Test the custom policies in your Azure AD B2C tenant.