JWT verification extension - #1402
Open
TristonianJones wants to merge 1 commit into
Open
Conversation
TristonianJones
force-pushed
the
jwt-support
branch
from
August 5, 2026 03:49
b31cec4 to
4feb61f
Compare
TristonianJones
commented
Aug 5, 2026
3 tasks
TristonianJones
force-pushed
the
jwt-support
branch
from
August 10, 2026 21:21
4feb61f to
856859a
Compare
TristonianJones
marked this pull request as ready for review
August 10, 2026 21:22
TristonianJones
force-pushed
the
jwt-support
branch
5 times, most recently
from
August 10, 2026 22:10
305f355 to
d0f5ff2
Compare
TristonianJones
force-pushed
the
jwt-support
branch
from
August 10, 2026 22:21
d0f5ff2 to
8e14e2c
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
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.
Support for JWT verification with automation key-fetching.
Introduce
jwt.Tokentype which models the structure of a JWT with aseries of well-defined claims accessible by their human-readable names
as well as support for optional claim-fetching.
As a best practice, you'll want to follow this flow:
jwt.verify(async) orjwt.verifyWithKey(sync)jwt.verify(token).presentedBy(aud, iss)