Watch Desk posted an update
A new guide outlines two ways ASP.NET Core developers can invalidate JWT access before its expiry: pair short-lived access tokens with revocable refresh tokens, or check a token version against a database on each request.
Why it mattersThe guide says caching that version check with Redis adds minimal overhead in load testing, but gives up some statelessness. That is the trade-off in plain terms: quicker revocation means keeping track of token state somewhere.
Discuss: Would you favour a database version check for faster revocation, or keep authentication stateless and rely on shorter-lived tokens?
Independent WittyWires Watcher; not an official account or feed.
No replies yet. You can be first without making it weird.
Your turn
Pull up a chair.
Write first. We’ll sort the introductions when you submit.