Skip to content

Commit 1411d01

Browse files
authored
Merge pull request #230511 from MicrosoftDocs/main
3/13 PM Publish
2 parents 3d48940 + a949d66 commit 1411d01

File tree

143 files changed

+1449
-979
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

143 files changed

+1449
-979
lines changed

.openpublishing.redirection.active-directory.json

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10941,6 +10941,11 @@
1094110941
"redirect_url": "/azure/active-directory-b2c/tenant-management-add-administrator",
1094210942
"redirect_document_id": false
1094310943
},
10944+
{
10945+
"source_path_from_root": "/articles/active-directory-b2c/support-options.md",
10946+
"redirect_url": "/azure/active-directory-b2c/find-help-open-support-ticket",
10947+
"redirect_document_id": false
10948+
},
1094410949
{
1094510950
"source_path": "articles/active-directory/managed-identities-azure-resources/how-to-manage-ua-identity-arm.md",
1094610951
"redirect_url": "/azure/active-directory/managed-identities-azure-resources/how-manage-user-assigned-managed-identities?pivots=identity-mi-methods-arm",

articles/active-directory-b2c/faq.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -259,4 +259,4 @@ sections:
259259
- question: |
260260
How do I report issues with Azure AD B2C?
261261
answer: |
262-
See [File support requests for Azure Active Directory B2C](support-options.md).
262+
See [File support requests for Azure Active Directory B2C](find-help-open-support-ticket.md).

articles/active-directory-b2c/find-help-open-support-ticket.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ manager: CelesteDG
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: troubleshooting
12-
ms.date: 03/30/2022
12+
ms.date: 03/13/2023
1313
ms.author: kengaderdus
1414
ms.subservice: B2C
1515
---
Lines changed: 85 additions & 115 deletions
Original file line numberDiff line numberDiff line change
@@ -1,164 +1,134 @@
11
---
2-
title: Tutorial to configure Azure Active Directory B2C with Haventec
2+
title: Configure Haventec Authenticate with Azure Active Directory B2C for single-step, multi-factor passwordless authentication
33
titleSuffix: Azure AD B2C
4-
description: Learn how to integrate Azure AD B2C authentication with Haventec for multifactor passwordless authentication
4+
description: Learn to integrate Azure AD B2C with Haventec Authenticate for multi-factor passwordless authentication
55
author: gargi-sinha
6-
manager: CelesteDG
6+
manager: martinco
77
ms.reviewer: kengaderdus
88
ms.service: active-directory
99
ms.workload: identity
1010
ms.topic: how-to
11-
ms.date: 12/02/2021
11+
ms.date: 03/10/2023
1212
ms.author: gasinh
1313
ms.subservice: B2C
1414
---
1515

16-
# Tutorial: Configure Haventec with Azure Active Directory B2C for single step, multifactor passwordless authentication
16+
# Tutorial: Configure Haventec Authenticate with Azure Active Directory B2C for single-step, multi-factor passwordless authentication
1717

18-
In this sample tutorial, learn how to integrate Azure Active Directory (AD) B2C authentication with [Haventec](https://www.haventec.com/). Haventec provides decentralized identity platform that transform security, accessibility, and experience. Haventec Authenticate provides a passwordless technology that eliminates passwords, shared secrets, and friction.
18+
Learn to integrate Azure Active Directory B2C (Azure AD B2C) with Haventec Authenticate, a passwordless technology that eliminates passwords, shared secrets, and friction.
1919

20-
## Scenario description
20+
To learn more, go to haventec.com: [Haventec](https://www.haventec.com/)
2121

22-
The Haventec integration includes the following components:
22+
## Scenario description
2323

24-
- Azure AD B2C - The authorization server, responsible for verifying the user's credentials, also known as the Identity Provider.
24+
The Authenticate integration includes the following components:
2525

26-
- Web and mobile applications - Any Open ID Connect (OIDC) mobile or web applications protected by Haventec and Azure AD B2C.
26+
* **Azure AD B2C** - authorization server that verifies user credentials
27+
* Also known as the identity provider (IdP)
28+
* **Web and mobile applications** - Open ID Connect (OIDC) mobile or web applications protected by Authenticate and Azure AD B2C
29+
* **Haventec Authenticate service** - external IdP for the Azure AD B2C tenant
2730

28-
- Haventec Authenticate service - Acts as the external Identity Provider to your Azure AD B2C tenant.
31+
The following diagram illustrates sign-up and sign-in user flows in the Haventec Authenticate integration.
2932

30-
The following architecture diagram shows the implementation.
33+
![Diagram of sign-up and sign-in user flows in the Haventec Authenticate integration.](media/partner-haventec/partner-haventec-architecture-diagram.png)
3134

32-
![Image shows the architecture diagram](media/partner-haventec/partner-haventec-architecture-diagram.png)
35+
1. User selects sign-in or sign-up and enters a username.
36+
2. The application sends user attributes to Azure AD B2C for identity verification.
37+
3. Azure AD B2C collects user attributes and sends them to Haventec Authenticate.
38+
4. For new users, Authenticate sends push notification to the user mobile device. It can send email with a one-time password (OTP) for device registration.
39+
5. User responds and is granted or denied access. New cryptographic keys are pushed to the user device for a future session.
3340

34-
| Steps | Description |
35-
|:----------------|:----------------------|
36-
| 1. | User arrives at a login page. Users select sign-in/sign-up and enter the username|
37-
| 2. | The application sends the user attributes to Azure AD B2C for identity verification.|
38-
| 3.| Azure AD B2C collects the user attributes and sends the attributes to Haventec to authenticate the user through the Haventec Authenticate app.|
39-
| 4. |For new users only, Haventec Authenticate sends a push notification to the registered users' mobile device. It can also send an email with an OTP for device registration.|
40-
| 5. | After the user responds to the push notification, the user is either granted or denied access to the customer application based on the verification results. New cryptographic keys are generated and pushed into the user's device to have it ready for the next session. |
41+
## Get started with Authenticate
4142

42-
## Onboard with Haventec
43+
Go to the haventec.com [Get a demo of Haventec Authenticate](https://www.haventec.com/products/get-started) page. In the personalized demo request form, indicate your interest in Azure AD B2C integration. An email arrives when the demo environment is ready.
4344

44-
Get in touch with Haventec to [request a demo](https://www.haventec.com/products/get-started). While filling out the request form, indicate that you want to onboard with Azure AD B2C. You'll be notified through email once your demo environment is ready.
45+
## Integrate Authenticate with Azure AD B2C
4546

46-
## Integrate Haventec with Azure AD B2C
47+
Use the following instructions to prepare for and integrate Azure AD B2C with Authenticate.
4748

4849
### Prerequisites
4950

50-
To get started, you'll need:
51-
52-
- An Azure AD subscription. If you don\'t have one, get a [free
53-
account](https://azure.microsoft.com/free/).
54-
55-
- An [Azure AD B2C tenant](tutorial-create-tenant.md) that is linked to your Azure subscription.
56-
57-
- A Haventec Authenticate [demo environment](https://www.haventec.com/products/get-started).
58-
59-
### Part - 1 Create an application registration in Haventec
60-
61-
If you haven't already done so, [register](tutorial-register-applications.md) a web application.
62-
63-
### Part - 2 Add a new Identity provider in Azure AD B2C
51+
To get started, you need:
6452

65-
1. Sign in to the [Azure portal](https://portal.azure.com/#home) as the global administrator of your Azure AD B2C tenant.
53+
* An Azure AD subscription
54+
* If you don't have one, get an [Azure free account](https://azure.microsoft.com/free/)
55+
* An Azure AD B2C tenant linked to the Azure subscription
56+
* see, [Tutorial: Create an Azure Active Directory B2C tenant](tutorial-create-tenant.md)
57+
* A Haventec Authenticate demo environment
58+
* See, [Get a demo of Haventec Authenticate](https://www.haventec.com/products/get-started)
6659

67-
2. Make sure you're using the directory that contains your Azure AD B2C tenant by selecting the **Directory + subscription** filter in the top menu and choosing the directory that contains your tenant.
60+
### Create a web application registration
6861

69-
3. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
62+
Before applications can interact with Azure AD B2C, register them in a tenant you manage.
7063

71-
4. Navigate to **Dashboard** > **Azure Active Directory B2C** > **Identity providers**.
64+
See, [Tutorial: Register a web application in Azure Active Directory B2C](tutorial-register-applications.md)
7265

73-
5. Select **New OpenID Connect Provider**.
66+
### Add a new identity provider in Azure AD B2C
7467

75-
6. Select **Add**.
68+
For the following instructions, use the directory with the Azure AD B2C tenant.
7669

77-
### Part - 3 Configure an Identity provider
70+
1. Sign in to the [Azure portal](https://portal.azure.com/#home) as the Global Administrator of your Azure AD B2C tenant.
71+
2. In the top menu, select **Directory + subscription**.
72+
3. Select the directory with the tenant.
73+
4. In the top-left corner of the Azure portal, select **All services**.
74+
5. Search for and select **Azure AD B2C**.
75+
6. Navigate to **Dashboard** > **Azure Active Directory B2C** > **Identity providers**.
76+
7. Select **New OpenID Connect Provider**.
77+
8. Select **Add**.
7878

79-
To configure an identity provider, follow these steps:
79+
### Configure an identity provider
8080

81-
1. Select **Identity provider type** > **OpenID Connect**
81+
To configure an identity provider:
8282

83-
2. Fill out the form to set up the Identity provider:
84-
85-
| Property | Value|
86-
|:--------------|:---------------|
87-
|Name |Enter Haventec or a name of your choice|
88-
|Metadata URL| `https://iam.demo.haventec.com/auth/realms/*your\_realm\_name*/.well-known/openid-configuration`|
89-
|Client ID | The application ID from the Haventec admin UI captured in Part - 1 |
90-
|Client Secret | The application Secret from the Haventec admin UI captured in Part - 1 |
91-
|Scope | OpenID email profile|
92-
|Response type | Code |
93-
|Response mode | forms_post |
94-
|Domain hint | Blank |
95-
96-
3. Select **OK**.
97-
98-
4. Select **Map this identity provider's claims**.
99-
100-
5. Fill out the form to map the Identity provider:
101-
102-
| Property | Value|
103-
|:--------------|:---------------|
104-
| User ID | From subscription |
105-
| Display name | From subscription |
106-
| Given name | given_name |
107-
| Surname | family_name |
108-
| Email | Email |
109-
110-
6. Select **Save** to complete the setup for your new OIDC Identity provider.
83+
1. Select **Identity provider type** > **OpenID Connect**.
84+
2. For **Name**, enter **Haventec**, or another name.
85+
3. For **Metadata URL**, use `https://iam.demo.haventec.com/auth/realms/*your\_realm\_name*/.well-known/openid-configuration`.
86+
4. For **Client ID**, enter the application ID recorded from the Haventec admin UI.
87+
5. For **Client Secret**, enter the application Secret recorded from the Haventec admin UI.
88+
6. For **Scope**, select **OpenID email profile**.
89+
7. For **Response type**, select **Code**.
90+
8. For **Response mode**, select **forms_post**.
91+
9. For **Domain hint**, leave blank.
92+
10. Select **OK**.
93+
11. Select **Map this identity provider's claims**.
94+
12. For **User ID**, select **From subscription**.
95+
13. For **Display** name, select **From subscription**.
96+
14. For **Given name**, use **given_name**.
97+
15. For **Surname**, use **family_name**.
98+
16. For **Email**, use **Email**.
99+
17. Select **Save**.
111100

112101
## Create a user flow policy
113102

114-
You should now see Haventec as a new OIDC Identity provider listed within your B2C identity providers.
115-
116-
1. In your Azure AD B2C tenant, under **Policies**, select **User flows**.
103+
For the following instructions, Haventec is a new OIDC identity provider in the B2C identity providers list.
117104

105+
1. In the Azure AD B2C tenant, under **Policies**, select **User flows**.
118106
2. Select **New user flow**.
119-
120107
3. Select **Sign up and sign in** > **version** > **Create**.
121-
122-
4. Enter a **Name** for your policy.
123-
124-
5. In the Identity providers section, select your newly created Haventec Identity provider.
125-
126-
6. Select **None** for Local Accounts to disable email and password-based authentication.
127-
128-
7. Select **Run user flow**
129-
130-
8. In the form, enter the Replying URL, for example, `https://jwt.ms`
131-
132-
9. The browser will be redirected to the Haventec login page
133-
134-
10. User will be asked to register if new or enter a PIN for an existing user.
135-
136-
11. Once the authentication challenge is accepted, the browser will redirect the user to the replying URL.
108+
4. Enter a **Name** for the policy.
109+
5. In **Identity providers**, select the created Haventec identity provider.
110+
6. For **Local Accounts**, select **None**. This selection disables email and password authentication.
111+
7. Select **Run user flow**.
112+
8. In the form, enter the replying URL, for example, `https://jwt.ms`.
113+
9. The browser redirects to the Haventec sign-in page.
114+
10. User is prompted to register, or enter a PIN.
115+
11. The authentication challenge is performed.
116+
12. The browser redirects to the replying URL.
137117

138118
## Test the user flow
139119

140-
Open the Azure AD B2C tenant and under Policies select **User flows**.
141-
142-
1. Select your previously created **User Flow**.
143-
144-
2. Select **Run user flow** and select the settings:
145-
146-
a. **Application**: select the registered app (sample is JWT)
147-
148-
b. **Reply URL**: select the redirect URL
149-
150-
c. Select **Run user flow**.
151-
152-
3. Go through sign-up flow and create an account
153-
154-
4. Haventec Authenticate will be called during the flow.
155-
156-
## Additional resources
120+
1. In the Azure AD B2C tenant, under **Policies**, select **User flows**.
121+
2. Select the created **User Flow**.
122+
3. Select **Run user flow**.
123+
4. For **Application**, select the registered app. The example is JWT.
124+
5. For **Reply URL**, select the redirect URL.
125+
6. Select **Run user flow**.
126+
7. Perform a sign-up flow and create an account.
127+
8. Haventec Authenticate is called.
157128

158-
For additional information, review the following articles:
129+
## Next steps
159130

160-
- [Haventec](https://docs.haventec.com/) documentation
131+
* Go to docs.haventec.com for [Haventec Documentation](https://docs.haventec.com/)
132+
* [Azure AD B2C custom policy overview](custom-policy-overview.md)
161133

162-
- [Custom policies in Azure AD B2C](custom-policy-overview.md)
163134

164-
- [Get started with custom policies in Azure AD B2C](custom-policy-get-started.md?tabs=applications)

0 commit comments

Comments
 (0)