What problems do you face with secure authentication?

Hey there everyone,

I'm a developer. I specialize in web and API development. I work with payments and much of our stuff has to pass certain reviews, etc.

I'm also working on building a startup that aims to solve authentication and authorization problems.

I'm curious as to what problems other developers are facing when building authentication or authorization into their projects.

For me, as an example, 2FA or MFA - it's a great tech to help prevent account takeovers from stolen credentials. But it's a pain in the ass for the user, the time based codes, etc. We've seen lower user adoption on services once we add 2FA/MFA - user's don't seem to want to "opt" into this.

Another example is passwords in general. The password complexity requirements, password life time, password history - it's not only a pain in the ass to property develop, but it's also a pain for the user. Then most people just write down a password anyway or put into a text file, then we're back to 2FA.

I would love to hear problems other developers are facing. This will help me build a better product and ensure developers and users are both happy.

Even more, if there are features or functions that could improve user flows, development time or other ideas, I would love to hear them!