fix: jwt regex validation error during skip-jwt-bearer-tokens flow #2888
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
tuunit
changed the title
tuunit
requested changes
Jan 8, 2025
Done |
…t with {
Related to issue oauth2-proxy#2887
tuunit
previously approved these changes
Jan 15, 2025
tuunit
changed the title
tuunit
approved these changes
Jan 15, 2025
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.
Change the jwttoken Regex
Description
Update jwt_session.go to just validate if each part of jwt token with {
Motivation and Context
Update jwt_session.go to just validate if each part of jwt token with {
Solve the issue:
#2887
How Has This Been Tested?
We test this on our local machine by building and running the oauth2-proxy.
Checklist: