You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In PR #57, the token exchange scope parameter is profiled to carry the purpose or intent of the transaction and its value is copied into the purp claim of the resulting Txn-Token.
Is this how we want to handle the 'purp' claim?
The text was updated successfully, but these errors were encountered:
I propose that the draft should allow value of the scope claim in the TraT request be independent of the purp claim in the TraT, because the requesting service may not know sufficient details about how the TraT is actually going to be used. For example, the requester may say the scope is "buy stock", whereas the purp claim could have a value like "equity trade"
In PR #57, the token exchange
scope
parameter is profiled to carry the purpose or intent of the transaction and its value is copied into thepurp
claim of the resulting Txn-Token.Is this how we want to handle the 'purp' claim?
The text was updated successfully, but these errors were encountered: