Skip to content

Commit acb33f1

Browse files
authored
Alt text
1 parent 4eb39ac commit acb33f1

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

articles/active-directory-b2c/partner-eid-me.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -57,7 +57,8 @@ The eID-Me apps authenticate users during transactions. The X509 public key auth
5757

5858
The following diagram illustrates eID-Me identity proofing, which occurs outside Azure AD B2C flows.
5959

60-
![Diagram of the identity proofing flow in eID-Me](./media/partner-eid-me/partner-eid-me-identity-proofing.png)
60+
![Diagram of the identity proofing flow in eID-Me.](./media/partner-eid-me/partner-eid-me-identity-proofing.png)
61+
6162

6263
1. User uploads a selfie to the eID-Me smartphone application.
6364
2. User scans and uploads a government issued identification document, such as passport or driver license, to the eID-Me smartphone application.
@@ -66,7 +67,8 @@ The following diagram illustrates eID-Me identity proofing, which occurs outside
6667

6768
The following diagram illustrates Azure AD B2C integration with eID-Me.
6869

69-
![Diagram of Azure AD B2C integration with eID-Me](./media/partner-eid-me/partner-eid-me-architecture-diagram.png)
70+
![Diagram of Azure AD B2C integration with eID-Me.](./media/partner-eid-me/partner-eid-me-architecture-diagram.png)
71+
7072

7173
1. User opens the Azure AD B2C sign-in page and signs in or signs up with a username.
7274
2. User forwarded to Azure AD B2C sign-in and sign-up policy.

0 commit comments

Comments
 (0)