An incoming JWT issued from a Token-Exchange procedure instead of a classical OAuth2 flow, adds a new act section but, other than that, contains all the keys a regular OAuth2 Access-Token:
act
iss
sub
exp
{ "iss": "decathlon.connect.eu-west-3.fewlines.co", "sub": "646c8f55-8803-49d8-8820-6bd2abf5451c", "exp": 1539012712, "act": { "sub": "<identifier-of-the-calling-application>" } }
Last updated 7 years ago