Re:Hardcoded secrets, unverified tokens, and other common JW...
by nextaccountic on Saturday June 27, 2020 @03:24PM
(#23663989)
Doing regular, boring authentication using user/password just supports logout out of box.
Re:Hardcoded secrets, unverified tokens, and other common JW...
by poxrud on Saturday June 27, 2020 @03:40PM
(#23664096)
So regular cookie session based auth? There are drawbacks such as managing session state on the server, and increased latency and cpu load, since you now have to have a db call on every action.
Re:Hardcoded secrets, unverified tokens, and other common JW...
by closeparen on Saturday June 27, 2020 @04:05PM
(#23664256)
The argument is that this DB call, or something much like it, is inherently necessary to support logout. It's not something unnecessary that can be optimized away; getting rid of it entails losing functionality.
OpenID Connect with JWT handles logout just fine if you really want it. Call the /oidc/tokeninfo to check the token is valid instead of verifying the signature offline. Of course this doesn't have the benefits of a decentralized token anymore. Can't have the cake and eat it too.