From 504c7ee1b6dd8a67fc62074084907798aedf6299 Mon Sep 17 00:00:00 2001 From: Oliver Terbu Date: Tue, 25 Jun 2024 09:57:54 +0200 Subject: [PATCH 1/9] fix: fixes #191 --- openid-4-verifiable-presentations-1_0.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md index 36358bae..9c6e34c5 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -791,6 +791,10 @@ This document also defines the following additional error codes and error descri - The value of the `request_uri_method` request parameter is neither `get` nor `post` (case-sensitive). +`wallet_unavailable`: + +- The Wallet could not respond to the request. + ## VP Token Validation From c40f7b3cd5882150422f5e0716bea6cbf7661a2b Mon Sep 17 00:00:00 2001 From: Oliver Terbu Date: Thu, 27 Jun 2024 08:57:54 +0200 Subject: [PATCH 2/9] applied @jogu and @peppelinux suggestions Co-authored-by: Joseph Heenan --- 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 9c6e34c5..8543bbad 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -793,7 +793,7 @@ This document also defines the following additional error codes and error descri `wallet_unavailable`: -- The Wallet could not respond to the request. +- The Wallet appears to be unavailable and therefore unable to respond to the request. ## VP Token Validation From 5bcd5027b5f2d2d73b8db6dafe05e051f4d4455d Mon Sep 17 00:00:00 2001 From: Oliver Terbu Date: Thu, 27 Jun 2024 14:20:34 +0200 Subject: [PATCH 3/9] fix: added more color on usage --- 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 8543bbad..c645a8b0 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -793,7 +793,7 @@ This document also defines the following additional error codes and error descri `wallet_unavailable`: -- The Wallet appears to be unavailable and therefore unable to respond to the request. +- The Wallet appears to be unavailable and therefore unable to respond to the request. This can be useful in situations where the user agent cannot invoke the Wallet, but the User wishes to continue the journey on the Verifier website. For example, this applies when using claimed HTTPS URIs that are handled by a component different from the Wallet because the platform cannot or does not translate the URI into a platform intent to invoke the Wallet. ## VP Token Validation From ef1ccfbfb4adf5221b71cd7bf6bc4bbf83207139 Mon Sep 17 00:00:00 2001 From: Oliver Terbu Date: Thu, 27 Jun 2024 14:39:29 +0200 Subject: [PATCH 4/9] fix: added privacy considerations --- openid-4-verifiable-presentations-1_0.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md index c645a8b0..e9520b5b 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -793,7 +793,7 @@ This document also defines the following additional error codes and error descri `wallet_unavailable`: -- The Wallet appears to be unavailable and therefore unable to respond to the request. This can be useful in situations where the user agent cannot invoke the Wallet, but the User wishes to continue the journey on the Verifier website. For example, this applies when using claimed HTTPS URIs that are handled by a component different from the Wallet because the platform cannot or does not translate the URI into a platform intent to invoke the Wallet. +- The Wallet appears to be unavailable and therefore unable to respond to the request. This can be useful in situations where the user agent cannot invoke the Wallet and another component receives the request while the user still controls the user experience and wishes to continue the journey on the Verifier website. For example, this applies when using claimed HTTPS URIs handled by the Wallet provider in case the platform cannot or does not translate the URI into a platform intent to invoke the Wallet. ## VP Token Validation @@ -1209,6 +1209,10 @@ Mandatory user interaction before sending the request, like clicking a button, u Requests from the Wallet to the Verifier SHOULD be sent with the minimal amount of information possible, and in particular, without any HTTP headers identifying the software used for the request (e.g., HTTP libraries or their versions). The Wallet MUST NOT send PII or any other data that could be used for fingerprinting to the Request URI in order to prevent user tracking. +## Authorization Error Response with Wallet unavailable error code + +In the event that another component is invoked instead of the Wallet while the user still controls the user experience, the user MUST be informed and give consent before returning the `wallet_unavailable` Authorization Error Response to the Verifier. + {backmatter} From 0d3594543130e0bb3382b62671e8739e7e1106eb Mon Sep 17 00:00:00 2001 From: Oliver Terbu Date: Fri, 5 Jul 2024 13:47:51 +0200 Subject: [PATCH 5/9] fix: incorporated feedback from jogu --- 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 e9520b5b..36b336f0 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -793,7 +793,7 @@ This document also defines the following additional error codes and error descri `wallet_unavailable`: -- The Wallet appears to be unavailable and therefore unable to respond to the request. This can be useful in situations where the user agent cannot invoke the Wallet and another component receives the request while the user still controls the user experience and wishes to continue the journey on the Verifier website. For example, this applies when using claimed HTTPS URIs handled by the Wallet provider in case the platform cannot or does not translate the URI into a platform intent to invoke the Wallet. +- The Wallet appears to be unavailable and therefore unable to respond to the request. This can be useful in situations where the user agent cannot invoke the Wallet and another component receives the request while and the user wishes to continue the journey on the Verifier website. For example, this applies when using claimed HTTPS URIs handled by the Wallet provider in case the platform cannot or does not translate the URI into a platform intent to invoke the Wallet. ## VP Token Validation @@ -1211,7 +1211,7 @@ Requests from the Wallet to the Verifier SHOULD be sent with the minimal amount ## Authorization Error Response with Wallet unavailable error code -In the event that another component is invoked instead of the Wallet while the user still controls the user experience, the user MUST be informed and give consent before returning the `wallet_unavailable` Authorization Error Response to the Verifier. +In the event that another component is invoked instead of the Wallet, the user MUST be informed and give consent before returning the `wallet_unavailable` Authorization Error Response to the Verifier. {backmatter} From c1157115361ad2ec1699c9190f8ccd4ccee3b643 Mon Sep 17 00:00:00 2001 From: Oliver Terbu Date: Mon, 15 Jul 2024 18:40:25 +0200 Subject: [PATCH 6/9] Update openid-4-verifiable-presentations-1_0.md Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com> --- 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 36b336f0..929aa3b9 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -1209,7 +1209,7 @@ Mandatory user interaction before sending the request, like clicking a button, u Requests from the Wallet to the Verifier SHOULD be sent with the minimal amount of information possible, and in particular, without any HTTP headers identifying the software used for the request (e.g., HTTP libraries or their versions). The Wallet MUST NOT send PII or any other data that could be used for fingerprinting to the Request URI in order to prevent user tracking. -## Authorization Error Response with Wallet unavailable error code +## Authorization Error Response with the `wallet_unavailable` error code In the event that another component is invoked instead of the Wallet, the user MUST be informed and give consent before returning the `wallet_unavailable` Authorization Error Response to the Verifier. From 1b4fad8a0a15acb1e4e0ced2a3265d6069e31346 Mon Sep 17 00:00:00 2001 From: Oliver Terbu Date: Mon, 15 Jul 2024 18:40:34 +0200 Subject: [PATCH 7/9] Update openid-4-verifiable-presentations-1_0.md Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com> --- 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 929aa3b9..7d77db90 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -793,7 +793,7 @@ This document also defines the following additional error codes and error descri `wallet_unavailable`: -- The Wallet appears to be unavailable and therefore unable to respond to the request. This can be useful in situations where the user agent cannot invoke the Wallet and another component receives the request while and the user wishes to continue the journey on the Verifier website. For example, this applies when using claimed HTTPS URIs handled by the Wallet provider in case the platform cannot or does not translate the URI into a platform intent to invoke the Wallet. +- The Wallet appears to be unavailable and therefore unable to respond to the request. It can be useful in situations where the User Agent cannot invoke the Wallet and another component receives the request while the End-User wishes to continue the journey on the Verifier website. For example, this applies when using claimed HTTPS URIs handled by the Wallet provider in case the platform cannot or does not translate the URI into a platform intent to invoke the Wallet. ## VP Token Validation From 7f0c14a92559076477ea3954dd2d366e2ec510bf Mon Sep 17 00:00:00 2001 From: Oliver Terbu Date: Tue, 16 Jul 2024 16:11:32 +0200 Subject: [PATCH 8/9] fix: clarified that the invoked component returns the error --- 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 7d77db90..1af32076 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -793,7 +793,7 @@ This document also defines the following additional error codes and error descri `wallet_unavailable`: -- The Wallet appears to be unavailable and therefore unable to respond to the request. It can be useful in situations where the User Agent cannot invoke the Wallet and another component receives the request while the End-User wishes to continue the journey on the Verifier website. For example, this applies when using claimed HTTPS URIs handled by the Wallet provider in case the platform cannot or does not translate the URI into a platform intent to invoke the Wallet. +- The Wallet appears to be unavailable and therefore unable to respond to the request. It can be useful in situations where the User Agent cannot invoke the Wallet and another component receives the request while the End-User wishes to continue the journey on the Verifier website. For example, this applies when using claimed HTTPS URIs handled by the Wallet provider in case the platform cannot or does not translate the URI into a platform intent to invoke the Wallet. In this case, the Wallet provider would return the Authorization Error Response to the Verifier and might redirect the User Agent back to the Verifier website. ## VP Token Validation @@ -1211,7 +1211,7 @@ Requests from the Wallet to the Verifier SHOULD be sent with the minimal amount ## Authorization Error Response with the `wallet_unavailable` error code -In the event that another component is invoked instead of the Wallet, the user MUST be informed and give consent before returning the `wallet_unavailable` Authorization Error Response to the Verifier. +In the event that another component is invoked instead of the Wallet, the user MUST be informed and give consent before the invoked component returns the `wallet_unavailable` Authorization Error Response to the Verifier. {backmatter} From 725180beca85073b3348838c738b7bdfbf71a674 Mon Sep 17 00:00:00 2001 From: Oliver Terbu Date: Tue, 16 Jul 2024 16:12:41 +0200 Subject: [PATCH 9/9] fix: updated doc history --- openid-4-verifiable-presentations-1_0.md | 1 + 1 file changed, 1 insertion(+) diff --git a/openid-4-verifiable-presentations-1_0.md b/openid-4-verifiable-presentations-1_0.md index 1af32076..fa039914 100644 --- a/openid-4-verifiable-presentations-1_0.md +++ b/openid-4-verifiable-presentations-1_0.md @@ -1909,6 +1909,7 @@ The technology described in this specification was made available from contribut * added references to ISO/IEC 23220 and 18013 documents * added `post` request method for Request URI * Added IETF SD-JWT VC profile + * Added `wallet_unavailable` error -20