Hey everyone I am using supertokens with nextjs and fastapi SuperTokens.com #support-questions-legacy

Hey everyone. I am using supertokens with nextjs a...

ikak1595

02/23/2023, 5:41 AM

Hey everyone. I am using supertokens with nextjs and fastapi with custom ui and the expiration of cookies is really weird. First of all my

st-last-access-token-update

sAccessToken

sFrontToken

are getting expired on

Mar 29 2024

(after almost 1 year), while my

sRefreshToken

is getting expired on

Jun 03 2023

(after almost 4 months). I have even set the validity in core config file:

Copy code

refresh_token_validity: 144000
access_token_validity: 3600

rp_st

02/23/2023, 5:44 AM

hey @ikak1595 those are cookie expiration times. Which is different from the actual token expiration time.

ikak1595

02/23/2023, 5:45 AM

But if I use the default ui, then the expiration time of the cookies is different.

rp_st

02/23/2023, 5:46 AM

hmm. That's odd

rp_st

02/23/2023, 5:46 AM

can you show me the sign in request's response headers?

rp_st

02/23/2023, 5:50 AM

and can you send the screenshot of the cookie store?

rp_st

02/23/2023, 5:54 AM

right. So i think this is a browser thing which sets it to a max of one year maybe. which is why it's setting to 2024. I'll have to check. That being said, the actual expiry of the token is checked based on the payload of the access token.

ikak1595

02/23/2023, 5:56 AM

Okay so that means the cookie's expiry is after an year but its value will expire after the time mentioned in core?

rp_st

02/23/2023, 5:56 AM

correct

ikak1595

02/23/2023, 5:57 AM

Okay thanks a lot

2 Views

Previous Next