extract idp from jwt in globalscale #714
Merged
Conversation
This file contains hidden or 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
ArtificialOwl
force-pushed
the
enh/noid/extract-idp-from-jwt
branch
from
58bebb5 to
f386f79
Compare
blizzz
approved these changes
Apr 20, 2023
ArtificialOwl
force-pushed
the
enh/noid/extract-idp-from-jwt
branch
from
f386f79 to
7db2a62
Compare
blizzz
approved these changes
Apr 20, 2023
blizzz
reviewed
Apr 20, 2023
|
/rebase |
Signed-off-by: Maxence Lange <maxence@artificial-owl.com>
blizzz
force-pushed
the
enh/noid/extract-idp-from-jwt
branch
from
7db2a62 to
c7fc204
Compare
|
rebased manually |
blizzz
approved these changes
May 22, 2023
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.
Because of the new behavior of clear() it seems necessary to extract the idp from the jwt string generated by globalsiteselector.