Add a 60-second leeway to the JWT validation logic #689
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.
What kind of change does this PR introduce? (check at least one)
When an identity provider (IDP) is implemented using the Authlib library, a machine client connecting to the IDP via the client credentials flow—using the client secret JWT or other JWT-based methods—may occasionally encounter an
Invalid client
error. This issue arises because the local time on the client's machine can sometimes be one or two seconds ahead of the IDP's time. As a result, theiat
claim in the client-signed JWT appears to be in the future, causing the IDP to reject it. To resolve this, a 60-second leeway can be added to the JWT validation logic.Does this PR introduce a breaking change? (check one)