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
So the HTTP entity body would represent the set of claims that needs to be appended to the set of claims Themis builds for a token.
If that's the case, one option is making this the source of highest precedence (that is, body > header > parameter for value overriding). I might have the order for header and parameter flipped here...
Context
Currently, Themis can only read in simple claim values from parameters.
For example, today you can tell Themis to "read in the value for this claim from the parameters" like so in config:
so when requesting a JWT
curl http://themis/issue?mac=1122334455566
you will get a JWT with the relevant claim:
Task
Now, say we want set the value of a claim called "human" to be something like:
To do so, the config would stay the same:
and on request (subject to change - more experimenting needed)
curl http:themis/issue?human.age=45&human.names=Awesome&human.names=Themis
a claim would be provided like so:
Notes:
The text was updated successfully, but these errors were encountered: