News for hackers. Stuff that matters.
Re:JWT is Awesome by drinchev on Tuesday February 18, 2020 @03:42PM (#22360176)
So where do you store the ones that should not allow to be refreshed? How short lived they should be in case of "Reset Password" scenario, when you need to kick out malicious user?
Re:JWT is Awesome by tracker1 on Tuesday February 18, 2020 @04:56PM (#22360802)
You can still do a redis or memcached, or even an rdbms table for that matter on revoked tokens... and do a lookup for critical systems... You don't need to do that on EVERY request though. It's really not less difficult than a session server/service/database, and more likely to scale better.
Re:JWT is Awesome by labawi on Tuesday February 18, 2020 @04:53PM (#22360775)
GP was talking about every request hitting the DB. A once in 10 min refresh should not be an issue.
Re:JWT is Awesome by kissgyorgy on Tuesday February 18, 2020 @04:03PM (#22360388)
that's the whole point. That's the trade off you make, you DON'T implement those features. When you need that, it doesn't make sense to use JWT. Right tools for the right job...