Closed aruehl closed 1 year ago
this is a duplicate of #814
Waiting for that release I suggest either putting leeway=1 in all your decode() calls, or limit your pyjwt <2.6.0 for now
this is a duplicate of #814 #814 got closed as the PR got closed but there was no release made yet.
Waiting for that release I suggest either putting leeway=1 in all your decode() calls, or limit your pyjwt <2.6.0 for now
this is a duplicate of #814 #814 got closed as the PR got closed but there was no release made yet.
Waiting for that release I suggest either putting leeway=1 in all your decode() calls, or limit your pyjwt <2.6.0 for now
Thanks and i also met this question and i just back to 2.5.0 and try again.
question: raise ImmatureSignatureError("The token is not yet valid (iat)") jwt.exceptions.ImmatureSignatureError: The token is not yet valid (iat)
Since upgrading to version 2.6.0 the decoding of my ID Token fails with: jwt.exceptions.ImmatureSignatureError: The token is not yet valid (iat)
The token has valid values. For example:
Epoch timestamp at calling the decode method was 1667737094. From client view the token is generated in the future.
Previous versions (2.4.0 and 2.5.0) are decoding the token susccessfully.
I have also tried
options={"verify_aud": False, "verify_nbf": False}
, but get the same error!Did you changed any parameters of validation?
Reproduction Steps
System Information