https://supertokens.com/
Join Discord
I was using the session with jwt enabled , i noticed one thing that the jwt expiry is default to 1 h...
# general
d
I was using the session with jwt enabled , i noticed one thing that the jwt expiry is default to 1 hr, in-spite of adding ACCESS_TOKEN_VALIDITY
r
Oh really! Can you please open an issue about this? May be a bug
d
r
Thank you. Will check it out asap.
d
My bad i closed the issue since the config error was on my end i had two core service running 😳
r
ahh right! Sounds good.
d
I did see that there is an off set of 30 seconds between the access token and jwt expiry, is this by design
r
yes. That is by design
Its there cause when you do 
getAccessTokenPayload()
, that decides if a refresh is needed based on the access token's lifetime. There might be an edge case where right before the access token is about to expire, you call the function, and it doesn't refresh. The resulting JWT in that case, if used to send to another service, can hence be expired. So to sort of relax this edge case a bit, we added an extra 30 secs to the JWT expiry.
2 Views
PreviousNext
Powered by

SuperTokens.com

SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

Powered by