From ef95f35965bc1b66fa30e5bb5a63b42fc7bad6c0 Mon Sep 17 00:00:00 2001 From: Joseph Heenan Date: Mon, 18 Mar 2024 13:17:21 -0400 Subject: [PATCH] Fix SIOPv2+VP example (#123) editorial. 3 approvals. open for more than a week. It should include vp_token in the response_type as per the table in section 6 ('Response'). closes #94 --- openid-4-verifiable-presentations-1_0.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md index 4f4ab646..2097418e 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -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 @@ -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