fix(introspect): exp, iat, nbf claims were always null #865
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
Lutonite
force-pushed
the
fix/introspect-date
branch
from
307d8f2 to
89629b8
Compare
|
not stale |
|
Thanks for the contribution! The change to the |
tronghn
approved these changes
Sep 5, 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.
Nimbus processed the JWT claims set to convert the "well-known" values to more appropriate formats, causing the introspection mapping to always return null for the expiration time, issue time, and not before time as the cast to Long could never succeed.
I've also noticed that while the audience is not strictly required to be an array, the claims map it as such either way, so I've adjusted the type for this as well.