Skip to content

Clarify terminate/reject/return error behaviours including for unsupported transaction_data #790

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jogu wants to merge 5 commits into
base: main
Choose a base branch
from
+16 −6
Open

Clarify terminate/reject/return error behaviours including for unsupported transaction_data #790

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
5 commits
Select commit Hold shift + click to select a range
bd66ebf
Clarify terminate, reject, and return an error behaviors
jogu Aug 27, 2026
15da9ea
Merge branch 'main' into clarify-terminate-reject-error
jogu Sep 10, 2026
d695dca
Address Jan's comment
jogu Sep 10, 2026
a294e61
Apply Frederik's suggestions to 1.1
jogu Sep 22, 2026
056c856
Mirror Frederik's suggestions to 1.0
jogu Sep 22, 2026
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
11 changes: 8 additions & 3 deletions 1.0/openid-4-verifiable-presentations-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -283,8 +283,8 @@ The Verifier communicates a Client Identifier Prefix that indicates how the Wall
Depending on the Client Identifier Prefix, the Verifier can communicate a JSON object with its metadata using the `client_metadata` parameter which contains name/value pairs.

Additional request parameters, other than those defined in this section, MAY be defined and used, as described in [@!RFC6749].
The Wallet MUST ignore any unrecognized parameters, other than the `transaction_data` parameter.
One exception to this rule is the `transaction_data` parameter. Wallets that do not support this parameter MUST reject requests that contain it.
The Wallet MUST ignore any unrecognized parameters.
One exception to this rule is the `transaction_data` parameter: a Wallet that does not support this parameter MUST reject requests that contain it, as defined in (#transaction_data).

## New Parameters {#new_parameters}
This specification defines the following new request parameters:
Expand Down Expand Up @@ -681,6 +681,8 @@ The Wallet MUST process the request as defined in [@RFC9101]. The Wallet SHOULD

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 Identifier value in the `client_id` Authorization Request parameter and the Request Object `client_id` claim value MUST be identical, including the Client Identifier Prefix. If any of these conditions are not met, the Wallet MUST terminate request processing.

When this specification requires the Wallet to terminate request processing (or terminate the process), the Wallet stops processing the request and MUST NOT return an Authorization Response or Authorization Error Response to the Verifier. In these situations, the Wallet was unable to obtain an authentic Authorization Request, so there is no trusted endpoint to which an Authorization Error Response could be sent.

The Wallet then validates the request as specified in OAuth 2.0 [@RFC6749].

### Request URI Error Response
Expand Down Expand Up @@ -1490,7 +1492,7 @@ The transaction data mechanism enables a binding between the user's identificati

The Wallet that received the `transaction_data` parameter in the request MUST include a representation or reference to the data in the respective Credential presentation. How this is done is transaction data type specific. Credential Formats can give recommendations of how to handle transaction data, such as those in (#format_specific_parameters).

If the Wallet does not support `transaction_data` parameter, it MUST return an error upon receiving a request that includes it.
If the Wallet does not support the `transaction_data` parameter, it MUST reject a request that includes it: the Wallet MUST NOT return a VP Token for such a request, and any response returned MUST be an error response using the error code `invalid_transaction_data` (see (#error-response)). As described in (#error-responses), the Wallet MAY instead cancel the flow without returning a response to the Verifier.

@c2bo c2bo Sep 28, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we want the MUST here for the error type? I guess we can always not return anything, but I am wondering if we absolutely want to restrict the error type here.

@c2bo c2bo Oct 1, 2026

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alternative:

Suggested change
If the Wallet does not support the `transaction_data` parameter, it MUST reject a request that includes it: the Wallet MUST NOT return a VP Token for such a request, and any response returned MUST be an error response using the error code `invalid_transaction_data` (see (#error-response)). As described in (#error-responses), the Wallet MAY instead cancel the flow without returning a response to the Verifier.
If the Wallet does not support the `transaction_data` parameter, it MUST reject a request that includes it: the Wallet MUST NOT return a VP Token for such a request, and any response returned SHOULD be an error response using the error code `invalid_transaction_data` (see (#error-response)). As described in (#error-responses), the Wallet MAY instead cancel the flow without returning a response to the Verifier.


## Error Response {#error-response}

Expand Down Expand Up @@ -1526,6 +1528,7 @@ This document also defines the following additional error codes and error descri

`invalid_transaction_data`:

- the Wallet does not support the `transaction_data` parameter, or
- any of the following is true for at least one object in the `transaction_data` structure:
- contains an unknown or unsupported transaction data type value,
- is an object of a known type but containing unknown fields,
Expand Down Expand Up @@ -3662,6 +3665,8 @@ The technology described in this specification was made available from contribut

-31

* Clarify that a Wallet terminating request processing does not return a response to the Verifier
* Clarify that a Wallet rejecting a request containing an unsupported `transaction_data` parameter uses the `invalid_transaction_data` error code if it returns an error response
* Clarify that a W3C Verifiable Credential requested without Cryptographic Holder Binding is returned directly in the VP Token, without a Verifiable Presentation
* add security considerations on untrusted input
* Clarify that the Wallet does not follow HTTP redirects
Expand Down
11 changes: 8 additions & 3 deletions 1.1/openid-4-verifiable-presentations-1_1.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -279,8 +279,8 @@ The Verifier communicates a Client Identifier Prefix that indicates how the Wall
Depending on the Client Identifier Prefix, the Verifier can communicate a JSON object with its metadata using the `client_metadata` parameter which contains name/value pairs.

Additional request parameters, other than those defined in this section, MAY be defined and used, as described in [@!RFC6749].
The Wallet MUST ignore any unrecognized parameters, other than the `transaction_data` parameter.
One exception to this rule is the `transaction_data` parameter. Wallets that do not support this parameter MUST reject requests that contain it.
The Wallet MUST ignore any unrecognized parameters.
One exception to this rule is the `transaction_data` parameter: a Wallet that does not support this parameter MUST reject requests that contain it, as defined in (#transaction_data).

## New Parameters {#new_parameters}
This specification defines the following new request parameters:
Expand Down Expand Up @@ -677,6 +677,8 @@ The Wallet MUST process the request as defined in [@RFC9101]. The Wallet SHOULD

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 Identifier value in the `client_id` Authorization Request parameter and the Request Object `client_id` claim value MUST be identical, including the Client Identifier Prefix. If any of these conditions are not met, the Wallet MUST terminate request processing.

When this specification requires the Wallet to terminate request processing (or terminate the process), the Wallet stops processing the request and MUST NOT return an Authorization Response or Authorization Error Response to the Verifier. In these situations, the Wallet was unable to obtain an authentic Authorization Request, so there is no trusted endpoint to which an Authorization Error Response could be sent.

The Wallet then validates the request as specified in OAuth 2.0 [@RFC6749].

### Request URI Error Response
Expand Down Expand Up @@ -1550,7 +1552,7 @@ The transaction data mechanism enables a binding between the user's identificati

The Wallet that received the `transaction_data` parameter in the request MUST include a representation or reference to the data in the respective Credential presentation. How this is done is transaction data type specific. Credential Formats can give recommendations of how to handle transaction data, such as those in (#format_specific_parameters).

If the Wallet does not support `transaction_data` parameter, it MUST return an error upon receiving a request that includes it.
If the Wallet does not support the `transaction_data` parameter, it MUST reject a request that includes it: the Wallet MUST NOT return a VP Token for such a request, and any response returned MUST be an error response using the error code `invalid_transaction_data` (see (#error-response)). As described in (#error-responses), the Wallet MAY instead cancel the flow without returning a response to the Verifier.

## Error Response {#error-response}

Expand Down Expand Up @@ -1586,6 +1588,7 @@ This document also defines the following additional error codes and error descri

`invalid_transaction_data`:

- the Wallet does not support the `transaction_data` parameter, or
- any of the following is true for at least one object in the `transaction_data` structure:
- contains an unknown or unsupported transaction data type value,
- is an object of a known type but containing unknown fields,
Expand Down Expand Up @@ -3734,6 +3737,8 @@ The technology described in this specification was made available from contribut

-01

* Clarify that a Wallet terminating request processing does not return a response to the Verifier
* Clarify that a Wallet rejecting a request containing an unsupported `transaction_data` parameter uses the `invalid_transaction_data` error code if it returns an error response
* Clarify that a W3C Verifiable Credential requested without Cryptographic Holder Binding is returned directly in the VP Token, without a Verifiable Presentation
* Clarify that the Wallet does not follow HTTP redirects
* Clarify jwks use parameter
Expand Down
Loading