News for hackers. Stuff that matters.
Re:Why to not use JWT (2021) by BigJono on Thursday September 29, 2022 @11:37AM (#33022184)
Think you misread, they were asking about the difference between a session ID in a cookie, and a bearer token. Not a session ID and a JWT.

With a bearer token each microservice still needs to call out to an auth service to validate the token, right?

Re:Why to not use JWT (2021) by slowmovintarget on Thursday September 29, 2022 @12:02PM (#33022548)
Funny thing about the terminology, JWT is just one kind of bearer token. The phrase bearer token in the first place simply means that if you have the token, assume you are who you say you are. (It's also shorthand for passing in the authorization HTTP request header with type "Bearer: ")

If you have an opaque token, then yes, you save nothing and still require a call to a central service.

Re:Why to not use JWT (2021) by sieabah on Thursday September 29, 2022 @01:13PM (#33023903)
If you share the hmac key or do private/public key signing you're able to distribute the public signing keys to your infra.

In doing so you just validate the token against the public key. You can then rotate these keys and have a list of them to validate against and age off keys which would be the last tokens expiration +1 day.

Re:Why to not use JWT (2021) by treis on Thursday September 29, 2022 @01:39PM (#33024382)
One bearer token can map to several session IDs.
Re:Why to not use JWT (2021) by foomatic2u on Friday September 30, 2022 @12:03AM (#33030782)
Or one bearer token can have one session Id. Depends on how you implement.