Set leeway on Datetime Claims creation #2182
Open
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.
Currently, the
leeway
property of Datetime claims is set after the instance creation, calling the relative setter method. This could cause validation errors inside thevalidateCreate
method of theIssuedAt
class, in the case where an instance gets created using a value from an existing token, due to the leeway not being considered.This has caused some problems on one of our services that was running on a pool of different hosts which happened to have their system clocks out of sync. We solved the issue by fixing our NTP configurations, but we'd appreciate the
leeway
property to be correctly handled by the library.The problem seems to be also mentioned here.
We really appreciate your effort with this project and we hope you find this helpful. I'm always available if you need me to further expand on this.
Have a nice weekend!