Using checkSession in client-side

Can token renewal (using checkSession) lead to token invalidation related to its signature in backend ?
I use checkSession every time jwt expiration time comes to an end and if user session is active , i just renew the token with checkSession and update it in my storage , so that following requests will be made with new token . Is it a common workflow ?

Yes, that’s a common approach, there should be no problems with it. One comment though:

renew the token with checkSession and update it in my storage

Tokens shouldn’t be stored in localStorage or sessionStorage, see:

Thanks a lot for quick response , i will keep in mind about storage.

1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.