“Long random tokens are the most overrated technology in authentication.”
Just so I follow, did you mean underrated…?
Re:OAuth 2.0 Authentication Vulnerabilities
by tptacek on Sunday March 28, 2021 @01:01PM
(#26611976)
Yeah, sorry!
Re:OAuth 2.0 Authentication Vulnerabilities
by laurent92 on Sunday March 28, 2021 @04:35AM
(#26608830)
But then you need to implement token revocation, by the host, the user or the client, and find a cryptographically-secure way to generate the key.
Re:OAuth 2.0 Authentication Vulnerabilities
by wolf550e on Sunday March 28, 2021 @05:13AM
(#26608951)
To revoke the token, the server deletes it from the database.
If you have the token, you can ask the server to delete it from the database. The cryptographically secure way to generate it is to read 32 bytes from getrandom(2) or from /dev/urandom.
you basically told somebody to roll his own crypto. that is a stupid idea. using refresh tokens and access tokens in a standard way is way more secure than rolling your own, this stuff is already pretty hard.
of course one could go with a simple cookie login, but when it comes to external apps, that's not always a good idea, especially not if you need to revoke specific applications.
so your general rule of thumb is pretty stupid.
A general rule of thumb w/r/t/ OAuth is that it starts to make sense when you are delegating authorization to other companies that share your users. Think "TweetLater".