News for hackers. Stuff that matters.
Re:Stop using JSON Web Tokens for user sessions by kaoD on Saturday November 25, 2023 @06:51AM (#38412933)
But again, what's the difference between that and just having a moderately-long access token if you'll still be handing out access tokens for the lifetime of the refresh token?
Re:Stop using JSON Web Tokens for user sessions by sseagull on Saturday November 25, 2023 @06:58AM (#38412968)
Another comment mentioned it, but:

1. You can check for user changes when the refresh token is used and a new access token is requested (user deleted, permissions changed, access revoked)

2. Refreshes can go to a different endpoint, whereas access tokens could be used with services that don’t even have access to user auth services.

Edit: There is something to be said for ditching the refresh token and just re-authenticating when the access token expires. The benefit is that you don’t need to store the username/password in the client code to re-auth, and you might avoid some relatively expensive password checking on the server, but that is probably pretty minor.

Re:Stop using JSON Web Tokens for user sessions by pests on Saturday November 25, 2023 @06:55AM (#38412958)
> for the lifetime of the refresh token

Not guaranteed for the lifetime of refresh tokens, which is the case for access tokens.

> whats the difference?

A 5 min access token is valid for 5 minutes. A 5 minute refresh token can be revoked before its even used.