Skip to content

Conversation

@alessandrodolci
Copy link

Currently, the leeway property of Datetime claims is set after the instance creation, calling the relative setter method. This could cause validation errors inside the validateCreate method of the IssuedAt 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!

@alessandrodolci alessandrodolci force-pushed the set-leeway-on-claim-creation branch from 9b32887 to b906044 Compare April 29, 2022 16:31
ArthurYdalgo added a commit to ArthurYdalgo/jwt-auth that referenced this pull request Jun 1, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant