fix: prefer RS256 for JWT validation#3695
Draft
olevski wants to merge 3 commits into
Draft
Conversation
Collaborator
Pull Request Test Coverage Report for Build 7660443831
💛 - Coveralls |
olevski
force-pushed
the
fix--use-RS256-for-token-validation
branch
6 times, most recently
from
January 25, 2024 17:11
0b5f406 to
23edee2
Compare
olevski
force-pushed
the
fix--use-RS256-for-token-validation
branch
from
January 25, 2024 20:06
4ad0354 to
c93d276
Compare
olevski
force-pushed
the
fix--use-RS256-for-token-validation
branch
from
January 25, 2024 21:05
c93d276 to
e3bb052
Compare
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 removes some unused old code that is not needed and adds JWT validation with RS256.
It is part of the gateway refactoring.
Still WIP.