4 ms·
> If you're a young CTO or early-stage engineer working on a web app If you're working on a greenfield login/auth, please don't accept and store passwords in a
by solatic 3y ago
> If you're a young CTO or early-stage engineer working on a web app
If you're working on a greenfield login/auth, please don't accept and store passwords in a database! Setup social OAuth, SSO, or magic link emails and make it someone else's problem.
- g_p 3y agoIf you do go down this route though, be sure to read up on what you're deploying, and understand what your libraries are doing (and more importantly, not doing). You don't want to end up with a naive implementation of OAuth2 (like some big names had recently) which fails to check the audience parameter, and therefore lets anyone other service using the same SSO gain access to your users' accounts. Recent HN post on this - https://news.ycombinator.com/item?id=38009291 https://news.ycombinator.com/item?id=38009291
- solatic 3y agoI agree, and thanks for pointing that out, but between the two security failures, I'd rather have an incorrect OAuth2 implementation, which can be quickly fixed with no impact on existing customers, than credential stuffing, where I need to email customers apologizing for why I needed to reset their passwords.