Add support for high-precision decimal TimeClaims #96
Conversation
This file contains 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
Nirusu
force-pushed
the
decimal-timeclaim
branch
from
4ff54c8 to
9e7366b
Compare
DolphFlynn
approved these changes
Jan 11, 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.
Some authentication providers issue JWTs with a higher precision than just seconds.
For example, Laravel Passport uses time values in microseconds, using a decimal number to represent this value in the JWT.
Currently, JWT Editor cannot parse these values, and displays them as Invalid Values in the information field.
This PR adds support for parsing those decimal high-precision timestamps, converting the decimal part into nanoseconds and adding it as
nanoAdjustmentinto the createdInstantobject.