You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/active-directory-b2c/partner-idemia.md
+11-10Lines changed: 11 additions & 10 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,12 @@ titleSuffix: Azure AD B2C
4
4
description: Learn to integrate Azure AD B2C authentication with IDEMIA Mobile ID for a relying party to consume Mobile ID, or US state-issued mobile IDs
5
5
services: active-directory-b2c
6
6
author: gargi-sinha
7
-
manager: CelesteDG
7
+
manager: martinco
8
8
ms.reviewer: kengaderdus
9
9
ms.service: active-directory
10
10
ms.workload: identity
11
11
ms.topic: how-to
12
-
ms.date: 03/08/2023
12
+
ms.date: 03/10/2023
13
13
ms.author: gasinh
14
14
ms.subservice: B2C
15
15
zone_pivot_groups: b2c-policy-type
@@ -35,7 +35,7 @@ Mobile ID integration includes the following components:
35
35
* It's also known as the identity provider (IdP)
36
36
***IDEMIA Mobile ID** - OpenID Connect (OIDC) provider configured as an Azure AD B2C external provider
37
37
* See, [Add an identity provider to your Azure AD B2C tenant](add-identity-provider.md)
38
-
***[IDEMIA Mobile ID application]** - a digital version of a driver’s license, or state-issued ID, in an app on your phone
38
+
***IDEMIA Mobile ID application** - a digital version of a driver’s license, or state-issued ID, in an app on your phone
39
39
* See, [IDEMIA Mobile ID](https://idemia-mobile-id.com/)
40
40
41
41
Mobile ID is a digitized identification document, a portable mobile identity token that DMVs use to verify individual identities. The signed digitized ID is stored on user mobile phones as an identity on the edge. The signed credentials ease access to identity services such as proof of age, financial know your customer, account access, etc.
@@ -58,6 +58,8 @@ To get started, go to the idemia.com [Get in touch](https://www.idemia.com/get-t
58
58
59
59
## Integrate Mobile ID with Azure AD B2C
60
60
61
+
Use the following sections to prepare for and perform integration processes.
62
+
61
63
## Prerequisites
62
64
63
65
To get started, you need:
@@ -70,9 +72,8 @@ To get started, you need:
70
72
* Your business web application registered in Azure AD B2C tenant.
71
73
* For testing, configure https://jwt.ms, a Microsoft-owned web application with decoded token contents.
72
74
73
-
74
75
>[!NOTE]
75
-
>The token contents never leave your browser.
76
+
>The token contents don't leave your browser.
76
77
77
78
### Submit a relying party application for mID
78
79
@@ -87,8 +88,8 @@ During Mobile ID integration, the following information is provided.
87
88
|Redirect URIs |`https://your-B2C-tenant-name.b2clogin.com/your-B2C-tenant-name.onmicrosoft.com/oauth2/authresp`<br>For example, `https://fabrikam.b2clogin.com/fabrikam.onmicrosoft.com/oauth2/authresp`<br><br>If you use a custom domain, enter `https://your-domain-name/your-tenant-name.onmicrosoft.com/oauth2/authresp`.|
88
89
|Post log out redirect URIs |`https://your-B2C-tenant-name.b2clogin.com/your-B2C-tenant-name.onmicrosoft.com/{policy}/oauth2/v2.0/logout`<br>Send a sign-out request. |
89
90
90
-
>[!NOTE]
91
-
>You need the Client ID and Client Secret later to configure the IdP in Azure AD B2C.
91
+
>[!NOTE]
92
+
>You need the Client ID and Client Secret later to configure the IdP in Azure AD B2C.
92
93
93
94
### Create a policy key
94
95
@@ -194,7 +195,7 @@ Azure AD B2C requests claims from the claims endpoint and returns them in the Ou
194
195
195
196
### Add a user journey
196
197
197
-
The IdP is set up, but it's not in any sign-in page. If you don't have a custom user journey, copy a template user journey.
198
+
For these instructions, the IdP is set up, but it's not in any sign-in page. If you don't have a custom user journey, copy a template user journey.
198
199
199
200
1. From the starter pack, open the `TrustFrameworkBase.xml` file.
200
201
2. Locate and copy the contents of the `UserJourneys` element, which includes `ID=SignUpOrSignIn`.
@@ -262,8 +263,8 @@ For the following instructions, use the directory with your Azure AD B2C tenant.
262
263
7. Select **Upload Custom Policy**.
263
264
8. Upload the two policy files you changed, in the following order:
264
265
265
-
* The extension policy, for example `TrustFrameworkExtensions.xml`
266
-
* The relying party policy, such as `SignUpSignIn.xml`
266
+
* The extension policy, for example `TrustFrameworkExtensions.xml`
267
+
* The relying party policy, such as `SignUpSignIn.xml`
0 commit comments