From d9a49d954d0b3b893aa939e8cd651340b1565393 Mon Sep 17 00:00:00 2001 From: Torsten Lodderstedt Date: Mon, 11 Mar 2024 18:33:07 +0100 Subject: [PATCH 1/4] Update openid-4-verifiable-presentations-1_0.md Co-authored-by: Daniel Fett --- openid-4-verifiable-presentations-1_0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md index b33b5df7..7c5e3926 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -515,7 +515,7 @@ The following is a non-normative example of a request object: "response_mode": "direct_post", "presentation_definition": {...}, "nonce": "n-0S6_WzA2Mj", - "state" : "eyJhb...6-sVA + "state" : "eyJhb...6-sVA" } ``` From 63d1f7ff98c070e643ca2b5843d55b887c67c4e3 Mon Sep 17 00:00:00 2001 From: Torsten Lodderstedt Date: Mon, 11 Mar 2024 18:33:15 +0100 Subject: [PATCH 2/4] Update openid-4-verifiable-presentations-1_0.md Co-authored-by: Daniel Fett --- openid-4-verifiable-presentations-1_0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md index 7c5e3926..a529dd18 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -519,7 +519,7 @@ The following is a non-normative example of a request object: } ``` -The Wallet MUST process the request process as defined in [@RFC9101]. Additionally, if the Wallet passed a `wallet_nonce` in the post request, the Wallet MUST validate whether the request object contains the respective nonce value in a `wallet_nonce`. If it does not, the Wallet MUST terminate request processing. +The Wallet MUST process the request as defined in [@RFC9101]. Additionally, if the Wallet passed a `wallet_nonce` in the post request, the Wallet MUST validate whether the request object contains the respective nonce value in a `wallet_nonce`. If it does not, the Wallet MUST terminate request processing. The request object MUST fulfill the requirements as defined in (#vp_token_request). From 6edd8d1a3d80c4bc8c478008689b258f1920b958 Mon Sep 17 00:00:00 2001 From: Torsten Lodderstedt Date: Mon, 11 Mar 2024 18:34:19 +0100 Subject: [PATCH 3/4] Update openid-4-verifiable-presentations-1_0.md Co-authored-by: Giuseppe De Marco --- openid-4-verifiable-presentations-1_0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md index a529dd18..0bb57b61 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -1168,7 +1168,7 @@ Whenever TLS is used, a TLS server certificate check MUST be performed, per [@!R ## Authorization Requests with Request URI -The Wallet MUST NOT sent personally identifiable information (PII) or any other data that could be used for fingerprinting to the Request URI in order to prevent user tracking. +The Wallet MUST NOT send personally identifiable information (PII) or any other data that could be used for fingerprinting to the Request URI in order to prevent user tracking. {backmatter} From e8a6cde853dc300e216f66cf16559c222492bd4a Mon Sep 17 00:00:00 2001 From: Torsten Lodderstedt Date: Mon, 11 Mar 2024 18:34:28 +0100 Subject: [PATCH 4/4] Update openid-4-verifiable-presentations-1_0.md Co-authored-by: Daniel Fett --- openid-4-verifiable-presentations-1_0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md index 0bb57b61..f8c95cdc 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -525,7 +525,7 @@ The request object MUST fulfill the requirements as defined in (#vp_token_reques The Wallet MUST extract the set of authorization request parameters from the Request Object. The Wallet MUST only use the parameters in this Request Object, even if the same parameter was provided in an authorization request query parameter. The Client ID value in the `client_id` authorization request parameter in the Request Object 'client_id' claim MUST be identical. If the Authorization Request contains a `client_id_scheme` parameter, the `client_id_scheme` authorization request parameter in the Request Object 'client_id_scheme' claim MUST be identical. If any of these conditions is not met, the Wallet MUST terminate request processing. -The Wallet then validates the request, as specified in OAuth 2.0 [RFC6749]. +The Wallet then validates the request as specified in OAuth 2.0 [@RFC6749]. ### Request URI Error Response