Hi George, Pieter, and Sean, I would like to share two GitHub issues I opened with two suggestions for draft-fletcher-transaction-token-chaining-profile:
1. Direct JAG-to-Txn-Token exchange as an optional flow When the downstream domain needs a local Txn-Token to continue the workflow, this issue explores whether the intermediate Access Token exchange can be avoided by allowing the downstream TTS to directly accept the JAG. In this proposal, no Txn-Token crosses the trust-domain boundary. Txn-Tokens remain local to their respective trust domains, while the JAG carries the cross-domain authorization information. https://github.com/gffletch/tt_xdomain/issues/17 2. Support `tctx` in `txn_claims` `tctx` may be useful for the downstream domain to continue the same workflow, so this proposes that it MAY be included in `txn_claims`, subject to minimization and privacy policy. https://github.com/gffletch/tt_xdomain/issues/18 I would appreciate your thoughts on these suggestions. Best regards, Yuan
_______________________________________________ OAuth mailing list -- [email protected] To unsubscribe send an email to [email protected]
