Skip to content

Commit fee3af8

Browse files
Merge pull request #252281 from cljung/cljung-vc-post-ga-08
upd on API retirement and presentation_verified
2 parents 85b2d61 + 3b0d107 commit fee3af8

File tree

2 files changed

+32
-1
lines changed

2 files changed

+32
-1
lines changed

articles/active-directory/verifiable-credentials/presentation-request-api.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -237,7 +237,9 @@ The following example demonstrates a callback payload after the verifiable crede
237237
},
238238
"domainValidation": {
239239
"url": "https://contoso.com/"
240-
}
240+
},
241+
"issuanceDate": "yyyy-MM-ddTHH:mm:ssZ",
242+
"expirationDate": "yyyy-MM-ddTHH:mm:ssZ"
241243
}
242244
],
243245
"receipt": {

articles/active-directory/verifiable-credentials/whats-new.md

Lines changed: 29 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -20,6 +20,35 @@ ms.author: barclayn
2020

2121
This article lists the latest features, improvements, and changes in the Microsoft Entra Verified ID service.
2222

23+
## September 2023
24+
25+
Verified ID is retiring old Request Service API endpoints that were available before Verified ID was General Available. These APIs should not have been used since GA in August 2022, but if they are used in your app, you need to migrate. The API endpoints being retired are:
26+
27+
```http
28+
POST https://verifiedid.did.msidentity.com/v1.0/:tenant/verifiablecredentials/request
29+
GET https://verifiedid.did.msidentity.com/v1.0/:tenant/verifiablecredentials/request/:requestId
30+
POST https://verifiedid.did.msidentity.com/v1.0/:tenant/verifiablecredentials/present
31+
POST https://verifiedid.did.msidentity.com/v1.0/:tenant/verifiablecredentials/issuance
32+
```
33+
34+
The first API was for creating an issuance or presentation request. The second API was for retrieving a request and the last two APIs was for a wallet completing issuance or presentation. The API endpoints to use since preview are the following.
35+
36+
```http
37+
POST https://verifiedid.did.msidentity.com/v1.0/:tenant/verifiablecredentials/createPresentationRequest
38+
POST https://verifiedid.did.msidentity.com/v1.0/:tenant/verifiablecredentials/createIssuanceRequest
39+
GET https://verifiedid.did.msidentity.com/v1.0/:tenant/verifiablecredentials/presentationRequests/:requestId
40+
POST https://verifiedid.did.msidentity.com/v1.0/:tenant/verifiablecredentials/completeIssuance
41+
POST https://verifiedid.did.msidentity.com/v1.0/:tenant/verifiablecredentials/verifyPresentation
42+
```
43+
44+
Please note that the `/request` API is split into two depending on if you are creating an issuance or presentation request.
45+
46+
The retired API endpoints will not work after October 2023, 2023.
47+
48+
## August 2023
49+
50+
The `presentation_verified` callback from the Request Service API now returns when a Verified ID credential was issued and when it expires. Business rules can use these values to see the time windoww of when the presented Verified ID credential is valid. An example of this is that it expires in an hour while the business required in needs to be valid until the end of the day.
51+
2352
## June 2023
2453

2554
Tutorial for getting started with the Wallet Library demo on Android and iOS available [here](using-wallet-library.md).

0 commit comments

Comments
 (0)