Skip to content

Clarify "request_context" #247

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
wants to merge 4 commits into
base: main
Choose a base branch
from
Open

Clarify "request_context" #247

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
b031088
Clarify "request_context"
PieterKas Sep 8, 2025
e31c559
Update draft-ietf-oauth-transaction-tokens.md
PieterKas Sep 17, 2025
25277f3
Update draft-ietf-oauth-transaction-tokens.md
PieterKas Oct 1, 2025
e3a5e73
Update draft-ietf-oauth-transaction-tokens.md
PieterKas Oct 1, 2025
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: 3 additions & 2 deletions draft-ietf-oauth-transaction-tokens.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -460,9 +460,9 @@ To request a Txn-Token the workload invokes the OAuth 2.0 {{RFC6749}} token endp
The type of the `subject_token` field is identified by `subject_token_type`.
* `subject_token_type` REQUIRED. The value MUST indicate the type of the token or value present in the `subject_token` parameter

The following additional parameters MAY be present in a Txn-Token Request:
The following additional parameters are RECOMMENDED to be present in a Txn-Token Request:

* `request_context` OPTIONAL. This parameter contains a base64url encoded JSON object which represents the context of this transaction. The parameter SHOULD be present and how the Transaction Token Service uses this parameter is out of scope for this specification.
* `request_context` OPTIONAL. This parameter contains a base64url encoded JSON object which represents the context of this transaction.
* `request_details` OPTIONAL. This parameter contains a base64url encoded JSON object which represents additional details of the transaction that MUST remain immutable throughout the processing of the transaction by multiple workloads. The Transaction Token Service uses this information to construct the `tctx` claim.

The requesting workload MUST authenticate its identity to the Transaction Token Service. The exact client authentication mechanism used is outside the scope of this specification.
Expand Down Expand Up @@ -740,6 +740,7 @@ The authors would like to thank the contributors and the OAuth working group mem
# Document History
{: numbered="false"}
[[ To be removed from final specification ]]
* Remove contradiction in "request_details" description and simpliffy normative langugage [Clarify claim usage](https://github.com/oauth-wg/oauth-transaction-tokens/issues/228).

## Since Draft 06
{:numbered="false"}
Expand Down