@rp_st Hi, i have a problem: supertokens token lifetime is not processed correctly in browsers. For example I have jwt with exp 1700223365, in data it is GMT: Friday, 17 November 2023 г., 12:16:05. But in browsers i have expiration Sat, 23 Dec 2023 22:16:06 GMT for this. So, while token has expired, browser does not try to refresh it and sends it to api, where it is expired. And my question is: why real expiration date in st-access-token payload much less than time that browsers decrypt themselves?

hey @IaS1506 this is expected, the API should return a 401 here and then that should trigger the refresh. The reason for this is that if the lifetime of the token in the browser was the same as thr access token lifetime, then in API calls, the broeser would not send the token, and it would be impossible to detect on the backend if the session exists, but requires a refresh vs a session deosn't exist,.

OK. it's just for my exprience, bc we have a lot of other problems using supertokens. So my company is transfering for self-written solution rigth now

oh! thats sad to hear. Can we get feedback on what all went wrong?

we have big cycles of refresh and email verify

hmmm. I see.

Yeah

what was the other thing that crashed?

we implement a thing with access token st-ev feature for time checking

hmm. These are strange issues. Im sure they can be fixed with some guidance, and id be happy to help out here.

Yeah, I could do this job like requesting you for support questions further\

alright! if you need our help, we are here to help 🙂

Just in case, I’ll ask: do you have any vacancies for developers from Russia? If I suddenly need to look for work 🙂

you could apply to us by emailing dixita@supertokens.com with your resume and a summary about what you are looking to do 🙂

ok, I'll keep it on mind