Feat: Custom JWT implementation #941
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
8000
…est with the `/userinfo` endpoint
# Conflicts: # Cargo.lock
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.
prerequisite for #857
With this PR, Rauthy has fully custom JWT creation / singing / verification. This made it possible to completely drop
jwt_simpleas a dependency, which removed 21 other external dependencies overall, and makes it possible to integrate PQC algorithms in the future. This custom impl also made all JWT related operations a lot more memory efficient and faster, with way less memory overhead and allocations.All integration tests are green again and I fixed a few minor other issues while doing the impl. The integration tests use an external crate to check the token validation, and it has been checked with other clients manually already as well.