Make encoding user groups in access tokens configurable #2085
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ishank011
force-pushed
the
jwt-token-reduce-size
branch
from
3dcbb3f to
bfe1d61
Compare
ishank011
changed the title
ishank011
force-pushed
the
jwt-token-reduce-size
branch
from
edfaef0 to
dfc453f
Compare
|
Size of token for user einstein (member of three groups):
|
glpatcern
approved these changes
Sep 21, 2021
|
Merging, since all the changes are controlled by a flag so we've ensured it doesn't break anything. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 PR adds a shared config parameter
skip_user_groups_in_tokenwhich can be used to control whether user groups should be encoded in the reva access tokens or not. If these are skipped, these are retrieved from theuserproviderservice and cached in the authentication interceptors, where these tokens are dismantled.Closes #2084