Skip to content
IAM Insights

Explainers · Glossary

txn claim

TXN claim · transaction identifier claim

Unique transaction ID claim in a Transaction Token, borrowed from Security Event Tokens, logged by every service for correlation.

In our briefings

The claim each of the newest briefings on txn claim would have you leave with.

  1. In the draft's main flow, a transaction token is minted once, at the edge of a trust domain, and passed on unchanged. The external-facing endpoint exchanges the inbound access token at the transaction token service (TTS) for a short-lived signed JWT. Its sub claim names the transaction's principal, the user or workload it is for, and its txn claim is a unique transaction identifier. Each workload that receives it must check the signature, audience and expiry, and must pass it downstream 'as it was received', in a dedicated Txn-Token header on HTTP calls. No claim is defined as a list of the hops along the way. req_wl is 'A string value that identifies the workload that requested' the token, and although a change-log entry says the authors 'Clarified how multiple workloads are represented in the req_wl claim', the definition says no more. It does allow replacement tokens, while warning that replacing them 'potentially negates the primary purpose of having Txn-Tokens', and a replacement must keep the call chain of the workloads that requested the replaced token, by a mechanism the draft leaves 'out of scope'. We read this as a token that names who a transaction is for and leaves the record of each hop to something else.

    Transaction Tokens carry who started a request through internal services and define no list of the hops in betweenBI-FIND-2026-0171

  2. Fletcher's rule for agents is not to hand them the user's credentials or access token, and to keep the agent's authentication apart from the authorization it carries. Where the agent then appears in a transaction token is open: the token can carry it, but "there is no profile that says we're going to call that claim X", and when a gateway rather than the agent requests the token the original caller has no standard place. He points to Ashay Raut's agents draft, which adds an actor chain and agent context, says Karl McGuinness's actor proposal probably needs merging with it, and notes that implementers already put the user and the agent the wrong way round between sub and act.

    Transaction tokens are nearly a standard, and there is still no agreed place in them for the agentBI-FIND-2026-0512

  3. Under RFC 9967 a SCIM event reports a change, and each receiver can choose its own follow-up; the authors say receivers do this "instead of interpreting SETs as commands". The deactivate event says a resource such as a User "has been deactivated and disabled", but its exact meaning SHOULD be agreed between the event publisher and the receiver. The RFC adds only that this typically means the subject may no longer have an active security session. The activate event "does not necessarily reflect any particular state change" either.

    RFC 9967 lets SCIM report a deactivated account and leaves what that means to each sender and receiverBI-FIND-2026-1697

Cited in 4 briefings

Every briefing that discusses this term, newest first.

  1. Transaction Tokens carry who started a request through internal services and define no list of the hops in between

    Draft · · IETF OAuth Working Group · Atul Tulshibagwale et al. · Jul 30, 2026

  2. Transaction tokens are nearly a standard, and there is still no agreed place in them for the agent

    Podcast · · Identity at the Center · #449 - Decoded - Transaction Tokens with George Fletcher · Sep 21, 2026

  3. RFC 9967 lets SCIM report a deactivated account and leaves what that means to each sender and receiver

    Article · · RFC Editor · Phil Hunt et al. · May 14, 2026

  4. Under RFC 8417 a security event token reports a fact, not an order, and the receiver decides what to do

    Article · · RFC Editor · Phil Hunt et al. · Jul 2018