Skip to content

Commit 1814915

Browse files
authored
Update partner-idemia.md
1 parent 4a717e0 commit 1814915

File tree

1 file changed

+11
-10
lines changed

1 file changed

+11
-10
lines changed

articles/active-directory-b2c/partner-idemia.md

Lines changed: 11 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -4,12 +4,12 @@ titleSuffix: Azure AD B2C
44
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
55
services: active-directory-b2c
66
author: gargi-sinha
7-
manager: CelesteDG
7+
manager: martinco
88
ms.reviewer: kengaderdus
99
ms.service: active-directory
1010
ms.workload: identity
1111
ms.topic: how-to
12-
ms.date: 03/08/2023
12+
ms.date: 03/10/2023
1313
ms.author: gasinh
1414
ms.subservice: B2C
1515
zone_pivot_groups: b2c-policy-type
@@ -35,7 +35,7 @@ Mobile ID integration includes the following components:
3535
* It's also known as the identity provider (IdP)
3636
* **IDEMIA Mobile ID** - OpenID Connect (OIDC) provider configured as an Azure AD B2C external provider
3737
* 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
3939
* See, [IDEMIA Mobile ID](https://idemia-mobile-id.com/)
4040

4141
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
5858

5959
## Integrate Mobile ID with Azure AD B2C
6060

61+
Use the following sections to prepare for and perform integration processes.
62+
6163
## Prerequisites
6264

6365
To get started, you need:
@@ -70,9 +72,8 @@ To get started, you need:
7072
* Your business web application registered in Azure AD B2C tenant.
7173
* For testing, configure https://jwt.ms, a Microsoft-owned web application with decoded token contents.
7274

73-
7475
>[!NOTE]
75-
>The token contents never leave your browser.
76+
>The token contents don't leave your browser.
7677
7778
### Submit a relying party application for mID
7879

@@ -87,8 +88,8 @@ During Mobile ID integration, the following information is provided.
8788
|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`.|
8889
|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. |
8990

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.
9293
9394
### Create a policy key
9495

@@ -194,7 +195,7 @@ Azure AD B2C requests claims from the claims endpoint and returns them in the Ou
194195

195196
### Add a user journey
196197

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.
198199

199200
1. From the starter pack, open the `TrustFrameworkBase.xml` file.
200201
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.
262263
7. Select **Upload Custom Policy**.
263264
8. Upload the two policy files you changed, in the following order:
264265

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`
267268

268269
### Test your custom policy
269270

0 commit comments

Comments
 (0)