Open GeekEast opened 3 years ago
I've been testing this, as I needed to know it as well.
Using the decoder at jwt.io and looks like if we ignore the expiresIn
key it is not including the exp
key in the token. So, I guess, meaning that the token won't expire.
weird for me verify
function literally does nothing, i've inserted a token without aud, sub and exp and he is not validating this, this is driving me crazy, WHY!?
Any update here?
What will happen if we did not set the expiresIn
?
According to the spec (https://datatracker.ietf.org/doc/html/rfc7519#section-4.1.4), exp
is an optional claim. So, if it's not defined, token is expired never.
Description
Currently, client can get a client via jwt signing withouth passing a
expiresIn
attribute. For example,So what's the default expiring date of the generated token? like after 24 hours, or it never expires?
Environment