Add clock_tolerance_seconds to M2M token authentication #326
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
jennifer-stytch
had a problem deploying
to
integration_tests
GitHub Actions
Failure
jennifer-stytch
had a problem deploying
to
integration_tests
GitHub Actions
Failure
vincent-stytch
approved these changes
Jul 22, 2024
jennifer-stytch
had a problem deploying
to
integration_tests
GitHub Actions
Failure
jennifer-stytch
had a problem deploying
to
integration_tests
GitHub Actions
Failure
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.
We occasionally see JWT validation errors with the
nbfclaim that may be due to clock skew. This PR adds theclock_tolerance_secondsparameter to the M2M token authentication method (it already existed for the local authentication method) to allow for some clock drift.