improvement: allow configuring extra claims for a user #1017
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is only half done. We still need to do one thing which is to modify the
store_in_session
helper toload_from_session
andassign_new_resources
to use the claims info from the session.This allows for
Now, in most setups, I would say not to store additional claims in the JWT and then actually use that information for authorization, but it is a legitimate optimization in many cases, or in situations where just being in possession of a given token is sufficient to authorize certain actions etc.