Don't test that JWT's issued in future are invalid #4678
Merged
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.
Remove two tests that JWT's whose
iat
value claims that they wereissued in the future fail validation.
These two tests fail on newer versions of PyJWT:
#4672
This is because PyJWT no longer raises an exception for future
iat
times:
jpadilla/pyjwt#190
PyJWT removed this validation because:
Clock skew can cause one party to generate
iat
times a few secondsor minutes ahead of another's current time
The JWT spec (RFC 7519) doesn't say that a JWT with a future
iat
should be considered invalid, these JWTs are valid
Other JWT libraries don't do this check