News for hackers. Stuff that matters.
Re:Loginsrv: JWT login microservice with back ends like OAut... by blahbhthrow3748 on Saturday May 23, 2020 @06:00PM (#23286928)
You basically need to have a revocation list or rely on the expiration time being sufficiently short. JWTs are neat for a lot of things but I don't think they make sense as a replacement for sessions for that reason (where you control the server and the client and you want to authenticate users)
Re:Loginsrv: JWT login microservice with back ends like OAut... by magicalhippo on Saturday May 23, 2020 @06:54PM (#23287325)
Isn't that the point of the refresh tokens? Auth token is short lived, so you get a new one using the refresh token without getting the user involved. But then that gives the auth server a means to deny that request if the user has revoked access?

Or am I misremembering?

Re:Loginsrv: JWT login microservice with back ends like OAut... by dchest on Sunday May 24, 2020 @06:12AM (#23290500)
Re:Loginsrv: JWT login microservice with back ends like OAut... by trebecks on Saturday May 23, 2020 @07:27PM (#23287566)
yeah, that is what refresh tokens are used for and it works well for access tokens with a short ttl. in practice i have seen access tokens with ttl of a few hours. i think it might be done to cut down on the refresh calls? in that case, if you want to deny requests with a revoked token sooner than the potentially few hours it takes for it to expire, you could keep the set of revoked tokens server side.

that feels like a weird place to be in with server side state for stuff that is supposed to be stateless. i guess the revoked set is smaller than the full set of active tokens so maybe that is a win? curious if anyone has experience with this.

Re:Loginsrv: JWT login microservice with back ends like OAut... by magicalhippo on Saturday May 23, 2020 @10:29PM (#23288594)
> in practice i have seen access tokens with ttl of a few hours

The JWT tokens we get for m2m from Maskinporten[1] have a TTL of a couple of minutes.

No refresh tokens though, I guess they figure it doesn't make much difference since the "user" is a machine so no hassle just sending a full request again.

[1]: https://difi.github.io/felleslosninger/maskinporten_protocol...

Re:Loginsrv: JWT login microservice with back ends like OAut... by bhl on Saturday May 23, 2020 @10:09PM (#23288487)
> the revoked set is smaller than the full set of active tokens so maybe that is a win

Yeah, it seems to me the difference between having a revocation / blacklist and a non-JWT based sessions isn't the number of queries to a redis cache, since each request to the resource server will result in a check first. It's the in-memory size of the cache.

I think that clears up my question about the benefits of using JWT. Thanks! :)