DEV Community

Discussion on: Can we talk about this feature? Please

Collapse
 
theaccordance profile image
Joe Mainwaring

If there’s one thing I’ve learned building and maintaining Auth features for the better part of a decade, it’s that I hate sinking tons of time into features that only support the primary value-add of your product. I would much rather at this point outsource Auth to a third party like Auth0 or Okta and factor the costs into my pricing model.

Even for personal projects, I’m using third-party Auth. This is partly because I already learned how to implement it, but in truth it didn’t take a lot to figure out. Probably equal to the happy path for writing my own - except I get the full package: user management, reset workflows, 2FA, etc.

Collapse
 
joelbonetr profile image
JoelBonetR 🥇

Well in this specific case (password recovery) you need to code almost everything anyway isn't it? 😅

You get an API which provides some ease of use in comparison but the workaround is up to you.

Collapse
 
theaccordance profile image
Joe Mainwaring

Depends on your chosen vendor! I’ve used Okta in the past for small projects and the entire feature (views, workflows, APIs) is owned by the vendor. They simply return to my app after authenticating.

Thread Thread
 
joelbonetr profile image
JoelBonetR 🥇 • Edited

Totally agree but that's just what most clients don't want 😅