Skip to content

Commit 083b265

Browse files
authored
Merge pull request #215737 from Gargi-Sinha/patch-143
Update partner-gallery.md
2 parents 8bcb0b1 + 3b8af89 commit 083b265

File tree

9 files changed

+118
-5
lines changed

9 files changed

+118
-5
lines changed

articles/active-directory/verifiable-credentials/TOC.yml

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,6 +66,8 @@
6666
href: howto-verifiable-credentials-partner-au10tix.md
6767
- name: LexisNexis
6868
href: howto-verifiable-credentials-partner-lexisnexis.md
69+
- name: Vu
70+
href: partner-vu.md
6971
- name: Samples
7072
expanded: true
7173
items:
@@ -108,4 +110,4 @@
108110
- name: Video overview of decentralized identities
109111
href: https://www.youtube.com/watch?v=Whc9Im-U0Wg
110112

111-
113+

articles/active-directory/verifiable-credentials/howto-verifiable-credentials-partner-au10tix.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,9 @@ As a developer you can share these steps with your tenant administrator to obtai
6666

6767
As a developer you now have the request URL and body from your tenant admin, follow these steps to update your application or website:
6868

69-
1. Add the request URL and body to your application or website to request Verified IDs from your users. Note: If you are using [one of the sample apps](https://aka.ms/vcsample), you'll need to replace the contents of the presentation_request_config.json with the request body obtained.
69+
1. Add the request URL and body to your application or website to request Verified IDs from your users.
70+
>[!Note]
71+
>If you are using [one of the sample apps](https://aka.ms/vcsample), you'll need to replace the contents of the `presentation_request_config.json` with the request body obtained in [Part 1](#part-1). The sample code overwrites the `trustedIssuers` values with `IssuerAuthority` value from `appsettings.json`. Copy the `trustedIssuers` value from the payload to `IssuerAuthority` in `appsettings.json` file.
7072
1. Be sure to replace the values for the "url", "state", and "api-key" with your respective values.
7173
1. [Grant permissions](verifiable-credentials-configure-tenant.md#grant-permissions-to-get-access-tokens) to your app to obtain access token for the Verified ID service request service principal.
7274

articles/active-directory/verifiable-credentials/howto-verifiable-credentials-partner-lexisnexis.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,8 +59,8 @@ As a developer you'll provide the steps below to your tenant administrator. The
5959
As a developer you now have the request URL and body from your tenant admin, follow these steps to update your application or website:
6060

6161
1. Add the request URL and body to your application or website to request Verified IDs from your users.
62-
>[!NOTE]
63-
> If you are using [one of the sample apps](https://aka.ms/vcsample) you need to replace the contents of the presentation_request_config.json with the request body obtained.
62+
>[!Note]
63+
>If you are using [one of the sample apps](https://aka.ms/vcsample), you'll need to replace the contents of the `presentation_request_config.json` with the request body obtained in [Part 1](#part-1). The sample code overwrites the `trustedIssuers` values with `IssuerAuthority` value from `appsettings.json`. Copy the `trustedIssuers` value from the payload to `IssuerAuthority` in `appsettings.json` file.
6464
1. Replace the values for the "url", "state", and "api-key" with your respective values.
6565
1. Grant your app [permissions](verifiable-credentials-configure-tenant.md#grant-permissions-to-get-access-tokens) to obtain an access token for the Verified ID service request service principal.
6666

2.78 KB
Loading
Binary file not shown.
395 KB
Loading
67 KB
Loading

articles/active-directory/verifiable-credentials/partner-gallery.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,8 +22,8 @@ To be considered into Entra Verified ID partner documentation, submit your appli
2222
|:-------------------------|:--------------|:--------------|
2323
|![Screenshot of au10tix logo.](media/partner-gallery/au10tix.png) | [AU10TIX](https://www.au10tix.com/solutions/microsoft-azure-active-directory-verifiable-credentials-program) improves Verifiability While Protecting Privacy For Businesses, Employees, Contractors, Vendors, And Customers. | [Configure Verified ID by AU10TIX as your Identity Verification Partner](https://aka.ms/au10tixvc). |
2424
| ![Screenshot of a LexisNexis logo.](media/partner-gallery/lexisnexis.png) | [LexisNexis](https://solutions.risk.lexisnexis.com/did-microsoft) risk solutions Verifiable credentials enables faster onboarding for employees, students, citizens, or others to access services. | [Configure Verified ID by LexisNexis Risk Solutions as your Identity Verification Partner](https://aka.ms/lexisnexisvc). |
25+
| ![Screenshot of a Vu logo.](media/partner-gallery/vu-logo.png) | [Vu](https://landings.vusecurity.com/microsoft-verifiable-credentials) verifiable credentials with just a selfie and your ID.| [Configure Verified ID by VU Identity Card as your Identity Verification Partner](partner-vu.md) |
2526
| ![Screenshot of a Onfido logo.](media/partner-gallery/onfido.jpeg) | [Onfido](https://onfido.com/landing/onfido-microsoft-idv-service/) Start issuing and accepting verifiable credentials in minutes. With verifiable credentials and Onfido you can verify a person’s identity while respecting privacy. Digitally validate information on a person’s ID or their biometrics.| * |
26-
| ![Screenshot of a Vu logo.](media/partner-gallery/vu.png) | [Vu Security](https://landings.vusecurity.com/microsoft-verifiable-credentials) Verifiable credentials with just a selfie and your ID.| * |
2727
| ![Screenshot of a Jumio logo.](media/partner-gallery/jumio.jpeg) | [Jumio](https://www.jumio.com/microsoft-verifiable-credentials/) is helping to support a new form of digital identity by Microsoft based on verifiable credentials and decentralized identifiers standards to let consumers verify once and use everywhere.| * |
2828
| ![Screenshot of a Idemia logo.](media/partner-gallery/idemia.png) | [Idemia](https://na.idemia.com/identity/verifiable-credentials/) Integration with Verified ID enables “Verify once, use everywhere” functionality.| * |
2929
| ![Screenshot of a Acuant logo.](media/partner-gallery/acuant.png) | [Acuant](https://www.acuant.com/microsoft-acuant-verifiable-credentials-my-digital-id/) - My Digital ID - Create Your Digital Identity Once, Use It Everywhere.| * |
Lines changed: 109 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,109 @@
1+
---
2+
title: Configure Verified ID by VU Identity Card as your Identity Verification Partner
3+
description: This article shows you the steps you need to follow to configure VU Identity Card as your identity verification partner
4+
services: active-directory
5+
author: gargi-sinha
6+
manager: martinco
7+
ms.service: decentralized-identity
8+
ms.subservice: verifiable-credentials
9+
ms.topic: how-to
10+
ms.date: 10/26/2022
11+
ms.author: gasinh
12+
# Customer intent: As a developer, I'm looking for information about the open standards that are supported by Microsoft Entra Verified ID.
13+
---
14+
15+
# Configure Verified ID by VU Identity Card as your Identity Verification Partner
16+
17+
In this article, we cover the steps needed to integrate Microsoft Entra Verified ID with VU Identity Card, a product of [VU Security](https://www.vusecurity.com/). VU Identity Card creates secure and frictionless digital experiences that enhance
18+
biometric onboarding and verification scenarios throughout the lifecycle
19+
of citizens and organizations.
20+
21+
VU Identity Card provides flexible and simple onboarding, authentication and
22+
verification processes on any device. It focuses on user experience and
23+
security without impacting the business.
24+
25+
To learn more about VU Security and its complete set of solutions, visit
26+
<https://www.vusecurity.com>
27+
28+
## Prerequisites
29+
30+
To get started with the VU Identity Card, ensure the following prerequisites are met:
31+
32+
- A tenant [configured](https://learn.microsoft.com/azure/active-directory/verifiable-credentials/verifiablee-credentials-configure-tenant)
33+
for Entra Verified ID service.
34+
35+
- If you don\'t have an existing tenant, you can [create an Azure
36+
account](https://azure.microsoft.com/free/?WT.mc_id=A261C142F)
37+
for free.
38+
39+
- The tenant must complete the VU Identity Card onboarding process.
40+
41+
- To create an account, [contact VU Security](https://landings.vusecurity.com/microsoft-verifiable-credentials/).
42+
43+
>[!Important]
44+
>Before you proceed, you must have received the URL from VU Security for users to be issued Verified IDs. If you have not yet received it, follow up with VU Security before you attempt following the steps documented in this article.
45+
46+
## Scenario description
47+
48+
VU Identity Card works as a link between users who need to access an application and applications that require secure access control, regardless of how users access the system.
49+
50+
Verifiable credentials can be used to enable faster and easier user onboarding by replacing some human interactions. For example, a user or employee who wants to create or remotely access an account can use a Verified ID through VU Identity Card to verify their identity without using vulnerable or overly complex passwords or the requirement to be on-site.
51+
52+
Learn more about [account onboarding](https://learn.microsoft.com/azure/active-directory/verifiable-credentials/plan-verification-solution#account-onboarding).
53+
54+
In this account onboarding scenario, Vu plays the Trusted ID proofing issuer role.
55+
56+
:::image type="content" source="media/partner-vu/vc-solution-architecture-diagram.png" alt-text="Diagram of the verifiable credential solution.":::
57+
58+
## Configure your application to use VU Identity Card
59+
60+
Follow these steps to incorporate VU Identity Card solution into your Apps.
61+
62+
### Part 1
63+
64+
As a developer you can share these steps with your tenant administrator to obtain the verification request URL, and body for your application or website to request Verified IDs from your users.
65+
66+
1. Go to Microsoft Entra portal - [**Verified ID**](https://entra.microsoft.com/#view/Microsoft_AAD_DecentralizedIdentity/ResourceOverviewBlade)
67+
68+
>[!NOTE]
69+
>Verify that the tenant configured for Verified ID meets the prerequisites.
70+
71+
2. Go to **Quickstart** > **Verification Request** >
72+
[**Start**](https://entra.microsoft.com/#view/Microsoft_AAD_DecentralizedIdentity/QuickStartVerifierBlade)
73+
74+
3. Choose **Select Issuer**.
75+
76+
4. Look for **VUSecurity** in the Search/select issuers
77+
drop-down.
78+
79+
[ ![Screenshot of the portal section used to choose issuers.](./media/partner-vu/select-issuers.png)](./media/partner-vu/select-issuers.png#lightbox)
80+
81+
5. Check the **VUIdentityCard** credential with the attributes
82+
such as firstname, lastname, number, country, gender, birth-date, and nationality or any other credential type.
83+
>[!NOTE]
84+
>Number attribute refers to National ID. For example, DNI-National Identification Number in Argentina.
85+
86+
6. Select **Add** and then select **Review**.
87+
88+
7. Download the request body and Copy/paste POST API request URL.
89+
90+
### Part 2
91+
92+
As a developer you now have the request URL and body from your tenant admin, follow these steps to update your application or website:
93+
94+
1. Add the request URL and body to your application or website to request Verified IDs from your users.
95+
>[!Note]
96+
>If you are using [one of the sample apps](https://aka.ms/vcsample), you'll need to replace the contents of the `presentation_request_config.json` with the request body obtained in [Part 1](#part-1). The sample code overwrites the `trustedIssuers` values with `IssuerAuthority` value from `appsettings.json`. Copy the `trustedIssuers` value from the payload to `IssuerAuthority` in `appsettings.json` file.
97+
98+
1. Be sure to replace the values for the **url**, **state**, and **api-key** with your respective values.
99+
100+
1. [Grant permissions](verifiable-credentials-configure-tenant.md#grant-permissions-to-get-access-tokens) to your app to obtain access token for the Verified ID service request service principal.
101+
102+
## Test the user flow
103+
104+
User flow is specific to your application or website. However if you are using one of the sample apps follow the steps outlined as part of the [sample app's documentation](https://aka.ms/vcsample).
105+
106+
## Next steps
107+
108+
- [Verifiable credentials admin API](admin-api.md)
109+
- [Request Service REST API issuance specification](issuance-request-api.md)

0 commit comments

Comments
 (0)