Tutorial for configuring HYPR with Azure Active Directory B2C
In this sample tutorial, we provide guidance on how to configure Azure AD B2C with HYPR. With Azure AD B2C as an identity provider, you can integrate HYPR with any of your customer applications to provide true passwordless authentication to your users. HYPR replaces passwords with Public key encryptions eliminating fraud, phishing, and credential reuse.
To get started, you'll need:
An Azure AD subscription. If you don't have a subscription, you can get a free account.
An Azure AD B2C tenant. Tenant is linked to your Azure subscription.
A HYPR cloud tenant, get a free trial account.
A user's mobile device registered using the HYPR REST APIs or the HYPR Device Manager in your HYPR tenant. For example, you can use the HYPR Java SDK to accomplish this task.
The HYRP integration includes the following components:
Azure AD B2C – The authorization server, responsible for verifying the user’s credentials, also known as the identity provider
Web and mobile applications - Your mobile or web applications that you choose to protect with HYPR and Azure AD B2C. HYPR provides a robust mobile SDK also a mobile app that you can use on iOS and Android platforms to do true passwordless authentication.
The HYPR mobile app - The HYPR mobile app can be used to execute this sample if prefer not to use the mobile SDKs in your own mobile applications.
HYPR REST APIs - You can use the HYPR APIs to do both user device registration and authentication. These APIs can be found here.
The following architecture diagram shows the implementation.
|1.||User arrives at a login page. Users select sign-in/sign-up and enter username into the page.|
|2.||The application sends the user attributes to Azure AD B2C for identify verification.|
|3.||Azure AD B2C collects the user attributes and sends the attributes to HYPR to authenticate the user through the HYPR mobile app.|
|4.||HYPR sends a push notification to the registered user mobile device for a Fast Identity Online (FIDO) certified authentication. It can be a user finger print, biometric or decentralized pin.|
|5.||After user acknowledges the push notification, user is either granted or denied access to the customer application based on the verification results.|
Configure the Azure AD B2C policy
Go to the Azure AD B2C HYPR policy in the Policy folder.
Configure the policy for the Azure AD B2C tenant.
Update the provided policies to relate to your specific tenant.
Test the user flow
Open the Azure AD B2C tenant and under Policies select Identity Experience Framework.
Select your previously created SignUpSignIn.
Select Run user flow and select the settings:
a. Application: select the registered app (sample is JWT)
b. Reply URL: select the redirect URL
c. Select Run user flow.
Go through sign-up flow and create an account
HYPR will be called during the flow, after user attribute is created. If the flow is incomplete, check that user isn't saved in the directory.
For additional information, review the following articles: