Skip to content

Commit fc04d56

Browse files
v-edmckillopv-edmckillop
authored
Update partner-nok-nok.md
1 parent bfc3b36 commit fc04d56

File tree

1 file changed

+62
-87
lines changed

1 file changed

+62
-87
lines changed

‎articles/active-directory-b2c/partner-nok-nok.md

Lines changed: 62 additions & 87 deletions
Original file line numberDiff line numberDiff line change
@@ -44,115 +44,90 @@ The following diagram illustrates the Nok Nok solution as IdP for Azure AD B2C u
4444
![Diagram of Nok Nok as IdP for Azure AD B2C using Open ID Connect (OIDC) for passwordless authentication.](./media/partner-nok-nok/nok-nok-architecture-diagram.png)
4545

4646
1. At the sign-in page, user selects sign-in or sign-up and enters the username.
47-
2. Azure AD B2C redirects user to the Nok Nok OIDC authentication provider. |
48-
| 3a. | For mobile based authentications, Nok Nok either displays a QR code or sends a push notification request to the end user’s mobile device. |
49-
| 3b. | For Desktop/PC based login, Nok Nok redirects the end user to the web application login page to initiate a passwordless authentication prompt. |
50-
|4a. | The user scan’s the displayed QR code in their smartphone using Nok Nok app SDK or Nok Nok Passport app.|
51-
| 4b. | User provides username as an input on the login page of the web application and selects next. |
52-
| 5a. | User is prompted for authentication on smartphone. <BR> User does passwordless authentication by using the user’s preferred method, such as biometrics, device PIN, or any roaming authenticator.|
53-
| 5b. | User is prompted for authentication on web application. <BR> User does passwordless authentication by using the user’s preferred method, such as biometrics, device PIN, or any roaming authenticator. |
54-
| 6. | Nok Nok server validates FIDO assertion and upon validation, sends OIDC authentication response to Azure AD B2C.|
55-
| 7. | Based on the response user is granted or denied access. |
47+
2. Azure AD B2C redirects user to the Nok Nok OIDC authentication provider.
48+
3. For mobile authentications, a QR code appears or push notification goes to the user device. For desktop sign-in, the user is redirected to the web app sign-in page for passwordless authentication.
49+
4. User scans the QR code with Nok Nok app SDK or Passport app. Or, username is sign-in page input.
50+
5. User is prompted for authentication. User does passwordless authentication: biometrics, device PIN, or any roaming authenticator. Authentication prompt appears on web application. User does passwordless authentication: biometrics, device PIN, or any roaming authenticator.
51+
6. Nok Nok server validates FIDO assertion and sends OIDC authentication response to Azure AD B2C.
52+
7. User is granted or denied access.
5653

5754
## Onboard with Nok Nok
5855

5956
Fill out the [Nok Nok cloud form](https://noknok.com/contact/) to create your own Nok Nok tenant. Once you submit the form, you'll receive an email explaining how to access your tenant. The email will also include access to Nok Nok guides. Follow the instructions provided in the Nok Nok integration guide to complete the OIDC configuration of your Nok Nok cloud tenant.
6057

6158
## Integrate with Azure AD B2C
6259

60+
Use the following instructions to add and configure an IdP then configure a user flow.
61+
6362
### Add a new Identity provider
6463

65-
To add a new Identity provider, follow these steps:
64+
For the following instructions, use the directory with the Azure AD B2C tenant. To add a new IdP:
6665

67-
1. Sign in to the **[Azure portal](https://portal.azure.com/#home)** as the global administrator of your Azure AD B2C tenant.
68-
1. Make sure you're using the directory that contains your Azure AD B2C tenant. Select the **Directories + subscriptions** icon in the portal toolbar.
69-
1. On the **Portal settings | Directories + subscriptions** page, find your Azure AD B2C directory in the **Directory name** list, and then select **Switch**.
70-
1. Choose **All services** in the top-left corner of the Azure portal, search for and select **Azure AD B2C**.
71-
1. Navigate to **Dashboard** > **Azure Active Directory B2C** > **Identity providers**
72-
1. Select **Identity providers**.
73-
1. Select **Add**.
66+
1. Sign in to the **[Azure portal](https://portal.azure.com/#home)** as Global Administrator of the Azure AD B2C tenant.
67+
2. In the portal toolbar, select the **Directories + subscriptions**.
68+
3. On **Portal settings, Directories + subscriptions**, in the **Directory name** list, locate the Azure AD B2C directory.
69+
4. Select **Switch**.
70+
5. In the top-left corner of the Azure portal, select **All services**.
71+
6. Search for and select **Azure AD B2C**.
72+
7. Navigate to **Dashboard** > **Azure Active Directory B2C** > **Identity providers**.
73+
8. Select **Identity providers**.
74+
9. Select **Add**.
7475

7576
### Configure an Identity provider
7677

77-
To configure an Identity provider, follow these steps:
78-
79-
1. Select **Identity provider type** > **OpenID Connect (Preview)**
80-
1. Fill out the form to set up the Identity provider:
81-
82-
|Property | Value |
83-
|:-----| :-----------|
84-
| Name | Nok Nok Authentication Provider |
85-
| Metadata URL | Insert the URI of the hosted Nok Nok Authentication app, followed by the specific path such as 'https://demo.noknok.com/mytenant/oidc/.well-known/openid-configuration' |
86-
| Client Secret | Use the client Secret provided by the Nok Nok platform.|
87-
| Client ID | Use the client ID provided by the Nok Nok platform.|
88-
| Scope | OpenID profile email |
89-
| Response type | code |
90-
| Response mode | form_post|
91-
92-
1. Select **OK**.
93-
94-
1. Select **Map this identity provider’s claims**.
95-
96-
1. Fill out the form to map the Identity provider:
97-
98-
|Property | Value |
99-
|:-----| :-----------|
100-
| UserID | From subscription |
101-
| Display name | From subscription |
102-
| Response mode | From subscription |
103-
104-
1. Select **Save** to complete the setup for your new OIDC Identity provider.
78+
To configure an IdP:
79+
80+
1. Select **Identity provider type** > **OpenID Connect (Preview)**.
81+
2. For **Name**, enter Nok Nok Authentication Provider, or another name.
82+
3. For **Metadata URL**, enter hosted Nok Nok Authentication app URI, followed by the path such as `https://demo.noknok.com/mytenant/oidc/.well-known/openid-configuration`
83+
4. For **Client Secret**, use the Client Secret from Nok Nok.
84+
5. For **Client ID**, use the client ID provided by Nok Nok.
85+
6. For **Scope**, use **OpenID profile email**.
86+
7. For **Response type**, use **code**.
87+
8. For **Response mode**, use **form_post**.
88+
9. Select **OK**.
89+
10. Select **Map this identity provider’s claims**.
90+
11. For **UserID**, select **From subscription**.
91+
12. For **Display name**, select **From subscription**.
92+
13. For **Response mode**, select **From subscription**.
93+
14. Select **Save**.
10594

10695
### Create a user flow policy
10796

108-
You should now see Nok Nok as a new OIDC Identity provider listed within your B2C identity providers.
97+
For the following instructions, Nok Nok is a new OIDC IdP in the B2C identity providers list.
10998

11099
1. In your Azure AD B2C tenant, under **Policies**, select **User flows**.
111-
112-
2. Select **New** user flow.
113-
114-
3. Select **Sign up and sign in**, select a **version**, and then select **Create**.
115-
116-
4. Enter a **Name** for your policy.
117-
118-
5. In the Identity providers section, select your newly created Nok Nok Identity provider.
119-
120-
6. Set up the parameters of your User flow. Insert a name and select the Identity provider you’ve created. You can also add email address. In this case, Azure won’t redirect the login procedure directly to Nok Nok instead it will show a screen where the user can choose the option they would like to use.
121-
122-
7. Leave the **Multi-factor Authentication** field as is.
123-
124-
8. Select **Enforce conditional access policies**
125-
126-
9. Under **User attributes and token claims**, select **Email Address** in the Collect attribute option. You can add all the attributes that Azure AD can collect about the user alongside the claims that Azure AD B2C can return to the client application.
127-
128-
10. Select **Create**.
129-
130-
11. After a successful creation, select your new **User flow**.
131-
132-
12. On the left panel, select **Application Claims**. Under options, tick the **email** checkbox and select **Save**.
100+
2. Select **New**.
101+
3. Select **Sign up and sign in**.
102+
4. Select a **version**.
103+
5. Select **Create**.
104+
6. Enter a policy **Name**.
105+
7. In **Identity providers**, select the created Nok Nok IdP.
106+
8. You can add an email address. Azure won't redirect sign-in to Nok Nok; a screen appears with user options.
107+
9. Leave the **Multi-factor Authentication** field.
108+
10. Select **Enforce conditional access policies**.
109+
11. Under **User attributes and token claims**, in the Collect attribute option, select **Email Address**.
110+
12. Add user attributes for Azure AD to collect, with claims that Azure AD B2C returns to the client application.
111+
13. Select **Create**.
112+
14. Select the new **User flow**.
113+
15. On the left panel, select **Application Claims**.
114+
16. Under options, select the **email** checkbox
115+
17. Select **Save**.
133116

134117
## Test the user flow
135118

136-
1. Open the Azure AD B2C tenant and under Policies select Identity Experience Framework.
137-
138-
2. Select your previously created SignUpSignIn.
139-
140-
3. Select Run user flow and select the settings:
119+
1. Open the Azure AD B2C tenant and under **Policies** select **Identity Experience Framework**.
120+
2. Select the created **SignUpSignIn**.
121+
3. Select **Run user flow**.
122+
4. For **Application**, select the registered app. The example is JWT.
123+
5. For **Reply URL**, select the redirect URL.
124+
6. Select **Run user flow**.
125+
7. Perform a sign-up flow and create an account.
126+
8. After the user attribute is created, Nok Nok is called.
141127

142-
a. Application: select the registered app (sample is JWT)
143-
144-
b. Reply URL: select the redirect URL
145-
146-
c. Select Run user flow.
147-
148-
4. Go through sign-up flow and create an account
149-
150-
5. Nok Nok 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.
128+
If the flow is incomplete, confirm the user is or isn't saved in the directory.
151129

152130
## Next steps
153131

154-
For additional information, review the following articles:
155-
156-
- [Custom policies in Azure AD B2C](./custom-policy-overview.md)
157-
158-
- [Get started with custom policies in Azure AD B2C](tutorial-create-user-flows.md?pivots=b2c-custom-policy)
132+
* [Azure AD B2C custom policy overview](./custom-policy-overview.md)
133+
* [Tutorial: Create user flows and custom policies in Azure Active Directory B2C](tutorial-create-user-flows.md?pivots=b2c-custom-policy)

0 commit comments

Comments
 (0)