Hi George, Pieter, Sean, I opened an issue on the profile about claims transcription: §7 covers sub, txn, scope, rctx and identity claims, but not tctx, so the claim class carrying the authorized operation has no transcription rule while the one carrying request environment does. Two consequences — tctx may be omitted entirely with §7.2/§9.5 still satisfied, and where it is carried its values are unconstrained. The issue proposes a §7.5 and notes the same question in draft-liu-oauth-cross-domain-txn-token, whose Figure 4 example is a stock trade.
https://github.com/gffletch/tt_xdomain/issues/20 Counterpart on the other draft: https://github.com/NiYuan224/draft-liu-oauth-cross-domain-txn-token/issues/3 I have negative conformance vectors for these transitions and am happy to contribute text or tests. Arjun Garg
_______________________________________________ OAuth mailing list -- [email protected] To unsubscribe send an email to [email protected]
