nbf check allows exact time matches. #88
Merged
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
|
Adding another snippet from http://self-issued.info/docs/draft-jones-json-web-token-06.html Section 4.1 Reserved Claim Names |
excpt
added a commit
that referenced
this pull request
Jul 3, 2015
nbf check allows exact time matches.
|
Thanks for the commit! 👍 |
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.
From the spec "The nbf (not before) claim identifies the time before which the JWT MUST NOT be accepted for processing.". The exact time is not before itself, so it should be valid.
This was annoying me in unit tests in a project of mine.