So yeah, once you start doing DB calls for every. single. request. you're going to have a lot more options, but JWTs are meant to avoid that.
My understanding is the "right" way to do this is to maintain a CRL.
So yeah, once you start doing DB calls for every. single. request. you're going to have a lot more options, but JWTs are meant to avoid that.
My understanding is the "right" way to do this is to maintain a CRL.
CRL is probably not going to help you. At least I have no idea. But jti's blacklist will. Don't forget - you still have to maintain and distribute it, which probably won't lead to a better implementation.
if you don't care about every request making an auth check, that's great! then just use basic sessions or whatever. there's no reason to use anything more complex
Also, DB calls are not necessary, when it comes to scaling, in-memory caching is a very valid option, so a DB read is only necessary occasionally.
Yes, you lose some of the benefits of JWT but that's inherently expected when using them for something that goes beyond their original capability.
everything else you mention is equally available in other, simpler, auth schemes