@rp_st need support, when we deploy Supertoken core to decrease access token validity from 30 days to one hour, we've got this error:

jwt invalid: failed to deserialize token claims: could not get token claims: go-jose/go-jose: unsupported key type/format

that's happen when and after we deploy it. Any reason why?

the spiek in refresh is cause you changed the access token lifetime to be smaller

so when we change access token, it will refresh all previous token that exists right after the Supertoken core deployment?

Not existing tokens. They will expire when they expire. But all new tokens will have that. Or, if you call mergeIntoAccessTokenPayload on existing sessions, the new tokens from that will also have that.

@rp_st I see, so its just for the newly expired token. I revert it for now. but confusingly, the number of 401 is high even after revert. I am still trying to understand the clock skew issue that you’ve mentioned above.

it doesnt create new ones on deployment, unless you have cleared the database