Skip to content

Commit

Permalink
Fix SIOPv2+VP example
Browse files Browse the repository at this point in the history
It should include vp_token in the response_type as per the table
in section 6 ('Response').

closes #94
  • Loading branch information
jogu committed Mar 5, 2024
1 parent 25a88fc commit 3738776
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions openid-4-verifiable-presentations-1_0.md
Original file line number Diff line number Diff line change
Expand Up @@ -1578,7 +1578,7 @@ The following is a non-normative example of a request that combines this specifi

```
GET /authorize?
response_type=id_token
response_type=vp_token%20id_token
&scope=openid
&id_token_type=subject_signed
&client_id=https%3A%2F%2Fclient.example.org%2Fcb
Expand All @@ -1590,7 +1590,7 @@ The following is a non-normative example of a request that combines this specifi

The differences to the example requests in the previous sections are:

* `response_type` is set to `id_token`. If the request also includes a `presentation_definition` parameter, the Wallet is supposed to return the `presentation_submission` and `vp_token` parameters in the same response as the `id_token` parameter.
* `response_type` is set to `vp_token id_token`. This means the Wallet returns the `presentation_submission` and `vp_token` parameters in the same response as the `id_token` parameter as described in (#response).
* The request includes the `scope` parameter with value `openid` making this an OpenID Connect request. Additionally, the request also contains the parameter `id_token_type` with value `subject_signed` requesting a Self-Issuer ID Token, i.e., the request is a SIOP request.

### Response
Expand Down

0 comments on commit 3738776

Please sign in to comment.