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/verifiable-credentials/admin-api.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -829,7 +829,7 @@ The response contains the following properties
829
829
830
830
| Property | Type | Description |
831
831
| -------- | -------- | -------- |
832
-
|`attestations`|[attestions](#attestations-type)| describing supported inputs for the rules |
832
+
|`attestations`|[attestations](#attestations-type)| describing supported inputs for the rules |
833
833
|`validityInterval`| number | this value shows the lifespan of the credential |
834
834
|`vc`| vcType array | types for this contract |
835
835
|`customStatusEndpoint`|[customStatusEndpoint] (#customstatusendpoint-type) (optional) | status endpoint to include in the verifiable credential for this contract |
@@ -840,8 +840,8 @@ If the property `customStatusEndpoint` property isn't specified then the `anonym
840
840
841
841
| Property | Type | Description |
842
842
| -------- | -------- | -------- |
843
-
|`idTokens`|[idTokenAttestation](#idtokenattestation-type) (array) (optional) | describes id token inputs|
844
-
|`idTokenHints`|[idTokenHintAttestation](#idtokenhintattestation-type) (array) (optional) | describes id token hint inputs |
843
+
|`idTokens`|[idTokenAttestation](#idtokenattestation-type) (array) (optional) | describes ID token inputs|
844
+
|`idTokenHints`|[idTokenHintAttestation](#idtokenhintattestation-type) (array) (optional) | describes ID token hint inputs |
Copy file name to clipboardExpand all lines: articles/active-directory/verifiable-credentials/how-to-dnsbind.md
+4-4Lines changed: 4 additions & 4 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -34,14 +34,14 @@ The domain you will verify ownership of to your DID is defined in the organizati
34
34
35
35
1. Copy or download the `did-configuration.json` file shown in the image below.
36
36
37
-
37
+
38
38
39
39
1. Host the `did-configuration.json` file at the location specified. Example: `https://www.example.com/.well-known/did-configuration.json`
40
40
There can be no additional path in the URL other than the .well-known path name.
41
41
42
42
1. When the `did-configuration.json` is publicly available at the .well-known/did-configuration.json URL, verify it by pressing the **Refresh verification status** button.
43
43
44
-
44
+
45
45
46
46
1. Test out issuing or presenting with Microsoft Authenticator to validate. Make sure the setting in Authenticator 'Warn about unsafe apps' is toggled on.
47
47
@@ -108,7 +108,7 @@ Before Microsoft Authenticator displays a **Verified** icon, a few things need t
108
108
109
109
If all of the previously mentioned are true, then Microsoft Authenticator displays a verified page and includes the domain that was validated.
Copy file name to clipboardExpand all lines: articles/active-directory/verifiable-credentials/presentation-request-api.md
+10-7Lines changed: 10 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -109,8 +109,8 @@ The payload contains the following properties.
109
109
110
110
|Parameter |Type | Description |
111
111
|---------|---------|---------|
112
-
|`includeQRCode`| Boolean | Determines whether a QR code is included in the response of this request. Present the QR code and ask the user to scan it. Scanning the QR code launches the authenticator app with this presentation request. Possible values are `true` (default) or `false`. When you set the value to `false`, use the return `url` property to render a deep link. |
113
-
|`includeReceipt`| Boolean | Determines whether a receipt should be included in the response of this request. Possible values are `true` or `false` (default). The receipt contains the original payload sent from the authenticator to the Verifiable Credentials service. The receipt is useful for troubleshooting or if you have the need to ge the full details of the payload. There's otherwise no need be set this value to `true `by default. In the `OpenId Connect SIOP` request, the receipt contains the ID token from the original request. |
112
+
|`includeQRCode`| Boolean |Optional. Determines whether a QR code is included in the response of this request. Present the QR code and ask the user to scan it. Scanning the QR code launches the authenticator app with this presentation request. Possible values are `true` (default) or `false`. When you set the value to `false`, use the return `url` property to render a deep link. |
113
+
|`includeReceipt`| Boolean |Optional. Determines whether a receipt should be included in the response of this request. Possible values are `true` or `false` (default). The receipt contains the original payload sent from the authenticator to the Verifiable Credentials service. The receipt is useful for troubleshooting or if you have the need to ge the full details of the payload. There's otherwise no need be set this value to `true `by default. In the `OpenId Connect SIOP` request, the receipt contains the ID token from the original request. |
114
114
|`authority`| string| Your decentralized identifier (DID) of your verifier Azure AD tenant. For more information, see [Gather tenant details to set up your sample application](verifiable-credentials-configure-verifier.md#gather-tenant-details-to-set-up-your-sample-application).|
115
115
|`registration`|[RequestRegistration](#requestregistration-type)| Provides information about the verifier. |
116
116
|`callback`|[Callback](#callback-type)| Mandatory. Allows the developer to update the UI during the verifiable credential presentation process. When the user completes the process, continue the process after the results are returned to the application.|
@@ -123,7 +123,10 @@ The `RequestRegistration` type provides information registration for the issuer.
123
123
124
124
|Property |Type |Description |
125
125
|---------|---------|---------|
126
-
|`clientName`| string| A display name of the issuer of the verifiable credential. This name will be presented to the user in the authenticator app. |
126
+
|`clientName`| string| A display name of the verifier of the verifiable credential. This name will be presented to the user in the authenticator app. |
127
+
|`purpose`| string| Optional. A string that is displayed to inform the user why the verifiable credentials are being requested. |
128
+
|`logoUrl`| URL| Optional. A URL for a logotype of the verifier. This is not used by the Authenticator app. |
129
+
|`termsOfServiceUrl`| URL| Optional. A URL to the terms of service for the verifier. This is not used by the Authenticator app. |
127
130
128
131
The following screenshot shows the `clientName` property and the display name of the `authority` (the verifier) in the presentation request.
129
132
@@ -146,8 +149,8 @@ The `RequestCredential` provides information about the requested credentials the
146
149
|Property |Type |Description |
147
150
|---------|---------|---------|
148
151
|`type`| string| The verifiable credential type. The `type` must match the type as defined in the `issuer` verifiable credential manifest (for example, `VerifiedCredentialExpert`). To get the issuer manifest, see [Gather credentials and environment details to set up your sample application](verifiable-credentials-configure-issuer.md). Copy the **Issue credential URL**, open it in a web browser, and check the **id** property. |
149
-
|`purpose`| string | Provide information about the purpose of requesting this verifiable credential. |
150
-
|`acceptedIssuers`| string collection | A collection of issuers' DIDs that could issue the type of verifiable credential that subjects can present. To get your issuer DID, see [Gather credentials and environment details to set up your sample application](verifiable-credentials-configure-issuer.md), and copy the value of the **Decentralized identifier (DID)**. If the `acceptedIssuers` collection is empty, then the presentation request will accept a credential type issued by any issuer. |
152
+
|`purpose`| string |Optional. Provide information about the purpose of requesting this verifiable credential. This is not used by the Authenticator app. |
153
+
|`acceptedIssuers`| string collection |Optional. A collection of issuers' DIDs that could issue the type of verifiable credential that subjects can present. To get your issuer DID, see [Gather credentials and environment details to set up your sample application](verifiable-credentials-configure-issuer.md), and copy the value of the **Decentralized identifier (DID)**. If the `acceptedIssuers` collection is empty or not present, then the presentation request will accept a credential type issued by any issuer. |
151
154
|`configuration.validation`|[Configuration.Validation](#configurationvalidation-type)| Optional settings for presentation validation.|
152
155
153
156
### Configuration.Validation type
@@ -156,8 +159,8 @@ The `Configuration.Validation` provides information about how the presented cred
156
159
157
160
|Property |Type |Description |
158
161
|---------|---------|---------|
159
-
|`allowRevoked`| Boolean | Determines if a revoked credential should be accepted. Default is `false` (it shouldn't be accepted). |
160
-
|`validateLinkedDomain`| Boolean | Determines if the linked domain should be validated. Default is `false`. Setting this flag to `false` means you as a Relying Party application accept credentials from an unverified linked domain. Setting this flag to `true` means the linked domain will be validated and only verified domains will be accepted. |
162
+
|`allowRevoked`| Boolean |Optional. Determines if a revoked credential should be accepted. Default is `false` (it shouldn't be accepted). |
163
+
|`validateLinkedDomain`| Boolean |Optional. Determines if the linked domain should be validated. Default is `false`. Setting this flag to `false` means you as a Relying Party application accept credentials from an unverified linked domain. Setting this flag to `true` means the linked domain will be validated and only verified domains will be accepted. |
|  | [Connect with Kocho. See Verified Identity in Action](https://kocho.co.uk/contact-us/)
32
-
[See Verified Identity in Action](https://kocho.co.uk/verified-id-in-action/) |
31
+
||[Connect with Kocho. See Verified Identity in Action](https://kocho.co.uk/contact-us/)<br/>[See Verified Identity in Action](https://kocho.co.uk/verified-id-in-action/)|
33
32
||[Verified ID - Predica Group](https://www.predicagroup.com/en/verified-id/)|
34
33
||[Sphereon supports customers on Microsoft's Entra Verified ID](https://sphereon.com/sphereon-supports-microsofts-entra-verified-id/)|
35
34
||[Microsoft Entra Verified ID - UNIFY Solutions](https://unifysolutions.net/entra/verified-id/)|
Copy file name to clipboardExpand all lines: articles/active-directory/verifiable-credentials/verifiable-credentials-configure-tenant.md
+3-3Lines changed: 3 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -61,7 +61,7 @@ After you create your key vault, Verifiable Credentials generates a set of keys
61
61
62
62
1. For **Key permissions**, verify that the following permissions are selected: **Create**, **Delete**, and **Sign**. By default, **Create** and **Delete** are already enabled. **Sign** should be the only key permission you need to update.
63
63
64
-
:::image type="content" source="media/verifiable-credentials-configure-tenant/set-key-vault-admin-access-policy.png" alt-text="Screenshot that shows how to configure the admin access policy." border="false":::
64
+
:::image type="content" source="media/verifiable-credentials-configure-tenant/set-key-vault-admin-access-policy.png" alt-text="Screenshot that shows how to configure the admin access policy." border="false":::
65
65
66
66
1. To save the changes, select **Save**.
67
67
@@ -165,8 +165,8 @@ After Azure Key Vault is setup, and the service have a signing key, you must com
165
165
166
166
1. Navigate to the Verified ID service in the Azure portal.
167
167
1. From the left menu, select **Setup**.
168
-
1. From the middle menu, select **Register decentralized ID** to register your DID document, as per instructions in articel[How to register your website ID for did:web](how-to-register-didwebsite.md). You must complete this step before you can continue to verify your domain. If you selected did:ion as your trust system, you should skip this step.
169
-
1. From the middle menu, select **Verify domain ownership** to verify your domain, as per instructions in articel [Link your domain to your Decentralized Identifier (DID)](how-to-dnsbind.md)
168
+
1. From the middle menu, select **Register decentralized ID** to register your DID document, as per instructions in article[How to register your decentralized ID for did:web](how-to-register-didwebsite.md). You must complete this step before you can continue to verify your domain. If you selected did:ion as your trust system, you should skip this step.
169
+
1. From the middle menu, select **Verify domain ownership** to verify your domain, as per instructions in article [Verify domain ownership to your Decentralized Identifier (DID)](how-to-dnsbind.md)
170
170
171
171
Once that you have successfully completed the verification steps, and have green checkmarks on all three steps, you are ready to continue to the next tutorial.
0 commit comments