Azure AD B2C Native Authentication
This comprehensive guide outlines the steps in configuring Azure AD B2C as an identity provider (IdP) within the EmpowerID platform. By integrating Azure AD B2C, EmpowerID users can seamlessly authenticate using their existing B2C credentials, enhancing security and streamlining the login process.
The guide provides instructions for registering an application in your Azure B2C tenant and configuring the necessary prerequisites. It also walks you through adding the Azure AD B2C OAuth IDP and its login button in EmpowerID.
Prerequisites
Please complete the following configurations in your Azure B2C tenant and gather the necessary configuration values before starting the setup.
Register an App Registration in Azure B2C Tenant
To configure EmpowerID's Azure B2C Native Auth, register a service provider application in your B2C tenant. Follow Microsoft's latest documentation or the guide Register a Microsoft Entra app and create a service principal. Ensure the following settings and configurations are completed correctly:
Redirect URIs – Set this value to the Fully Qualified Domain Name (FQDN) of your EmpowerID Server.
API Permission – Grant the service principal the necessary Microsoft Graph API permissions for Azure AD B2C Native Auth. These permissions include:
offline_access – Maintain access to data you have given access to.
openid – Sign users in.
Access Token & ID Token Issuance: Ensure the app is configured to issue both Access Tokens and ID Tokens.
Ensure that these attributes are gathered as you proceed with the setup, as they will be required when registering the OAuth Identity Provider (IDP) in EmpowerID:
EmpowerID Attribute | Description |
---|---|
Consumer Key | Application (client) ID of the Azure app registration you created while registering the service principal application. |
Consumer Secret | Secret ID of the secret you created for the Azure app registration in the above Prerequisites steps. |
Configure UserInfo Endpoint
EmpowerID requires the UserInfo endpoint to retrieve user data. However, unlike Azure AD, Azure AD B2C does not support the UserInfo endpoint by default. To enable this, the Identity Experience Framework must be configured with custom policies that return data through the UserInfo endpoint. Refer to the Microsoft documentation below to set up these custom policies, or check the latest guidance to configure the UserInfo endpoint correctly. https://learn.microsoft.com/en-us/azure/active-directory-b2c/userinfo-endpoint?pivots=b2c-custom-policy
Ensure that these attributes are gathered as you proceed with the setup, as they will be required along with previously collected configuration attributes when registering the OAuth Identity Provider (IDP) in EmpowerID:
EmpowerID Attribute | Description |
---|---|
Sender Identifier | The UserInfo endpoint URL you configured. A typical login endpoint appears as contractorsplatformauth.examplelogin.com/contractorsplatform.onmicrosoft.com/b2c_1a_auth_flow. The first part (contractorsplatformauth.examplelogin.com) is the custom domain for the authentication service, while the second part (contractorsplatform.onmicrosoft.com) shows the default Azure tenant domain. The last part (b2c_1a_auth_flow) points to a specific user flow that handles both sign-in and sign-up operations, ensuring a seamless login experience for users. |
Step 1 – Set up OAuth IDP in EmpowerID
Please follow the instructions below to set up OAuth IDP in EmpowerID.
Support for Multiple Tenants
You can now add multiple tenants within the same OAuth definition. This enhancement allows you to include multiple tenants in a single definition, which was not possible previously. To do this, simply repeat the process of adding the OAuth definition as outlined in Step #3 below for each tenant you want to include. This streamlines the configuration process and makes it easier to manage multiple tenants within the same setup.
URL Replacement to Resolve Tenant
The Authorize URL (v1) of the Azure AD B2C is https://{0}/oauth2/v2.0/authorize. In this URL, the value you provide in the Sender Identifier will replace the parameter {0}. Therefore, the Sender Identifier is crucial for directing users to the correct tenant login URL in Azure B2C. Ensure that the Sender Identifier is set correctly to facilitate seamless authentication for the designated tenant.
Navigate to Oauth Services
On the navbar, expand Apps and Authentication > SSO Connections and click OAuth / OpenID Connect.
Select the External OAuth Services tab and then search for AzureADB2C.
Click the Provider link for AzureADB2C.
Details of B2C Authentication
The default configuration for B2C authentication will be displayed on the details page. Find the Add button and click on it to proceed with adding details.Add OAuth Service
The default configuration for B2C authentication will be displayed on the details page. To add a new authentication provider, follow these steps:Name: Provide a unique and descriptive identifier for the service.
Display Name: Provide a clear and user-friendly label.
Consumer Key: Enter the Application (client) ID from the Azure app registration you created while registering the service principal application.
Consumer Secret: Enter the Secret ID of the secret you created for the Azure app registration.
Is Identity Provider: Select the checkbox to configure it as an identity provider.
Existing Account Directory: Select the existing Account Directory or choose the AzureGlobalIdP if the B2C tenant is not managed within the EmpowerID system.
Select Existing OAuth Scope: Please remember to select the default OAuth Scope, which is "AzureADB2C".
Callback URL: Enter the FQDN of your EmpowerID server. The value should look similar to
https://sso.empoweriam.com/WebIdPForms/OAuth/V2
.Sender Identifier: Enter the UserInfo endpoint URL you configured.
Description: Provide a brief explanation of the authentication provider.
Â
Save Configuration.
Please remember to click the save button.
Step 2 – Add a Login Button for Azure AD B2C Native Authentication
Expand Apps and Authentication > SSO Connections on the navbar and click SSO Components.
Select the IdP Domains tab and click the IdP Domains link for the IDP Domain where you want the Login button to appear.
Â
Select the External OAuth Providers tab and then the Azure AD B2C Authentication providers. To apply multiple providers, select multiple checkboxes.Â
Click Save.
Step 3 - Verify the Auth Provider is Working
The account needs to be inventoried by EmpowerID. It can be an account that hasn’t been joined to a person, but it should still be inventoried, even if it’s an orphan account.
Access the EmpowerID Portal:
Open the EmpowerID portal, and on the login screen, confirm that the login tile for the Azure AD B2C provider is visible.Authenticate via Azure AD B2C:
Click on the Azure AD B2C authentication tile and log in using your Azure AD B2C credentials. Ensure that valid B2C identifiers are used during login.Confirm Successful Login:
Upon successful authentication, you should be directed to the EmpowerID dashboard. Verify that you can access the dashboard and that the login process works as expected.
This ensures that the configuration for Azure AD B2C authentication is functioning properly.
IN THIS ARTICLE