Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 1 addition & 4 deletions 1.0/openid-4-verifiable-presentations-1_0.md
Original file line number Diff line number Diff line change
Expand Up @@ -1465,10 +1465,6 @@ If the Wallet does not support `transaction_data` parameter, it MUST return an e

The error response follows the rules as defined in [@!RFC6749], with the following additional clarifications:

`invalid_scope`:

- Requested scope value is invalid, unknown, or malformed.

`invalid_request`:

- The request contains both a `dcql_query` parameter and a `scope` parameter referencing a DCQL query.
Expand Down Expand Up @@ -3595,6 +3591,7 @@ The technology described in this specification was made available from contribut
-31

* Clarify that `encrypted_response_enc_values_supported` applies only if JWE content encryption algorithm is used
* Removed invalid_scope error guidance as duplicate of RFC6749
* Clarified that Multi-RP-sig section means Verifier Info instead of attestations
* Updated origin examples to remove trailing slash
* Clarify that `aud` corresponds to `issuer` Wallet Metadata paremeter if Dynamic Discovery is used
Expand Down
5 changes: 1 addition & 4 deletions 1.1/openid-4-verifiable-presentations-1_1.md
Original file line number Diff line number Diff line change
Expand Up @@ -1525,10 +1525,6 @@ If the Wallet does not support `transaction_data` parameter, it MUST return an e

The error response follows the rules as defined in [@!RFC6749], with the following additional clarifications:

`invalid_scope`:

- Requested scope value is invalid, unknown, or malformed.

`invalid_request`:

- The request contains both a `dcql_query` parameter and a `scope` parameter referencing a DCQL query.
Expand Down Expand Up @@ -3663,6 +3659,7 @@ The technology described in this specification was made available from contribut
* Add security consideration not to use VP Token as Access Token
* Clarify that `encrypted_response_enc_values_supported` applies only if JWE content encryption algorithm is used; e.g., it does not apply to JOSE HPKE
* Clarify that `aud` corresponds to `issuer` Wallet Metadata paremeter if Dynamic Discovery is used
* Removed invalid_scope error guidance as duplicate of RFC6749
* Clarified that Multi-RP-sig section means Verifier Info instead of attestations
* Updated origin examples to remove trailing slash
* Clarified that request_uri_method is a case-sensitive string
Loading