Discussion

Lazy JWT Key Rotation in .NET: Redis-Powered JWKS That Just Works

time4tea: The key material is in redis? Seems odd. Should be in fips 140 hsm? Else key can be stolen easy.Maybe missed something.

a_random_name: (glanced at it so I could be wrong) They're talking about a public key that can be used to validate the JWT's authenticity. AFAIK there is no need to keep these secret, and it's not possible to (without breaking public key crypto) forge them so it should be safe to store them wherever.

nijave: How can the key be stolen easily? That really depends on the security of the Redis setup. Redis is typically not internet accessible so you'd need some sort of server exploit.

legulere: Much simpler: just store session ids in Redis.I skimmed over the previous articles in this blog and they don't seem to mention the one use case JWTs were made for: having a separate authentication server from the application server. Most developers will only need this for integrating into corporations with single sign in or social logins (sign in with Facebook/google/apple...). There you won't write the authentication server but integrate with them. Session Ids are dead simple to get right securely. Just use them.