|
Charles Wilt wrote:
Useful reading (this is part 2, can skip part 1 if you have a basichttps://supertokens.io/blog/the-best-way-to-securely-manage-user-sessions
understanding of JWT and user sessions)
On Wed, Apr 21, 2021 at 5:23 AM Tim Fathers <tim@xxxxxxxxxxxxx> wrote:
better that I have been able to - I mean talk about over engineered! It
To be honest, I feel the post [above] actually makes my point rather
literally says it's non-trivial to implement a token refresh mechanism,
which is mostly only there because stateless tokens can't be revoked.
I found a bunch of other sources which corroborate Tim's position.
Perhaps the easiest to digest is this:
https://blog.logrocket.com/jwt-authentication-best-practices/
That one also links to a couple of other good ones, longer but still
quite accessible:
https://developer.okta.com/blog/2017/08/17/why-jwts-suck-as-session-tokens
http://cryto.net/~joepie91/blog/2016/06/13/stop-using-jwt-for-sessions/
Note that the last one does NOT support HTTPS, which means some
browsers or browser extensions will complain that you're about to
follow an unsafe link, which is slightly ironic.
I do not have the technical knowledge to evaluate whether a
complicated scheme like that used by SuperTokens does indeed buy you
better session security compared to older, simpler, more battle-tested
schemes. It's unquestionably complex. On the plus side, SuperTokens
has already packaged up their system into something you can download
for free and host yourself. It might even work directly on IBM i with
Node.js (I have not confirmed this).
One thing stressed by almost all the articles which recommend against
JWT for sessions is that JWT is uncontroversially well-suited for
certain other uses, such as authenticating API calls.
John Y.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.