[Openid-specs-ab] AB/C WG Pacific Meeting Notes (2025-08-04)

[george at practicalidentity.com]

> On Aug 5, 2025, at 2:25 AM, Nat Sakimura via Openid-specs-ab <openid-specs-ab at lists.openid.net> wrote:
> 
> Transaction Identifier Claim
> Proposer: Dima Postnikov
> Background: trx Claim was removed from eKYC specification as too generic for identity assurance
> Use Case: Commercial ecosystems need to trace transactions after performance, especially for identity sharing
> Existing Work: References SEC events transaction identifier
> Proposal: Create a separate OpenID Connect specification to define usage in ID tokens
> Process: Michael offered to help create GitHub repository for the specification
> Precedent: Referenced unmet authentication requirements spec that defined only an error code
> 
How is this claim different from that being used in the OAuth Transaction Tokens spec as specified by the Security Event Token RFC 8417 section 2.2?


   "txn" (Transaction Identifier) Claim
      An OPTIONAL string value that represents a unique transaction
      identifier.  In cases in which multiple related JWTs are issued,
      the transaction identifier claim can be used to correlate these
      related JWTs.  Note that this claim can be used in JWTs that are
      SETs and also in JWTs using non-SET profiles.



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-ab/attachments/20250805/ae7acc2b/attachment.htm>