feat(jwt): support RSA-PSS signatures (PS256/PS384/PS512)#336
Merged
Conversation
EdSchouten
reviewed
May 7, 2026
Member
EdSchouten
left a comment
EdSchouten
left a comment
There was a problem hiding this comment.
Just checking: RS* and PS* always use the same JSON Web Keys? No distinct formats between the two? If so, then it's fine to keep this all implemented by a single type.
Contributor
Author
That's my understanding, asked an LLM to be sure:
Pushed the alphabetical sort as new commit, feel free to squash-merge |
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 PR adds RSA-PSS (PS256/PS384/PS512) verification to the JWT validator, alongside the existing PKCS#1 v1.5 (RS256/RS384/RS512) support.
We want to support an internal identity provider that signs tokens with PSS.