Handling Long-Living Refresh Tokens in JWT Authentication After Cookie Clearance
I’m implementing JWT authentication in a web application for a university project, and I’ve encountered an issue with the management of refresh tokens when a user clears their cookies before these tokens naturally expire. I would appreciate some guidance or suggestions on alternative approaches.