NotBefore value in token is very recent

JWT.io
1

I’m having a problem, the NotBefore value in the jwt has a very recent value.
So if the server has a minimal (milliseconds) out of sync with auth0 server the token is not valid.
Okta for example generates the NotBefore with 5 minutes delay so you don’t have that problem.

Is there any way to change this behavior in auth0?

3

Hi @nrebagliati,

Welcome to the Auth0 Community!

Most of our SDKs allow a leeway parameter to account for a bit of clock skew. If you provide some information about your setup I can help you track down the docs for it.

4

Ok, the python library that I’m using it don’t implement any leeway.
Thanks

1 Like