Does this bother you too?

Ruby on Rails developers are able to turn to Devise. It does exactly what you seem to want it to do, and a decade later, it's still excellent.

There are many solutions, depending what tools you use. In general, heavier back-end frameworks like Django (for Python) or Laravel (for PHP) have built-in solutions or well established authentication/authorization libraries.

My product does this for Node/React. You can generate a codebase with Firebase auth, forgot pass flow, UI, etc. Optionally, you can add more features like subscription payments if you'd like a full SaaS app.

What if you just want to use static sites? Firebase or Netlify only?

Yes, this is exactly why we took what we we had and wrapped in a SaaS explicitly for other indie hackers.

We couldn't stand the pricing or complexity of the solutions in this space. While we focused on our core users pain (access control), it provides session management flows for user auth with most login providers.

Authress

How about using "AWS Cognito"? Not only you can use for all the simple stuff but you can integrate "Sign in with... [Google|Facebook|...]". There is some learning curve but once you done, it the same process all the time

Laravel Jetstream all the way and you'll never have this problem again.

Have you tried memberstack.io ? They are positioned as working with no code platforms but also have an API for simple user sign up, login, and also subscriptions. Slightly niche use case but really quickly and lovely UI

@Maheshwari S recently posted about Flutter Starter, which I've been looking into. It handles all the auth stuff you mentioned along with some template code for making API calls. Especially helpful for a Flutter beginner like myself, they organize directories for you to know the proper way to organize a production size application.

Definitely bugs me - I feel like I've built out user management 10 times over.
I'm looking at using Outseta or Memberstack for the next tool I build

Yup, it bothers me too.
Mostly, I'm using Laravel (PHP) to build a new project. It included with the authentication package, you can choose the community version and paid version.

The auth package really fastens the development. The problem is I need to integrate a new template for the different projects depends on client preferences.

Of course, I have an admin panel to manage basic data like users, articles, etc. But, theming is really time-consuming.

Shoutout to https://mernkit.com as a decent starter. In the end it didn't quite have everything I need and I preferred to roll my own solution, but at just $9.99 a month compared to most boilerplates that are like $700, it's worth taking a peek.

I wrote this once in a node backend. For my next project, Im going to strip it out and reuse the user admin and auth infrastructure. The frontend will have to be redone but I'll just copy+paste the service file and then write the UI from scratch.

Best of both worlds here. I wrote it once to learn how it's actually done, but then each project will have a unique UI going forward. I expect I'll refine the backend part as time goes on. Take inspiration from woodworkers here and build yourself jigs you can reuse across projects. Another example of this is I might develop a collection of UI components over time to reuse in projects, since I plan on staying married to react for my projects.

Up until the release of Laravel Jetstream (PHP) I've had this issue too. I was busy writing a small boilerplate to develop SaaS solutions quickly. But then Laravel Jetstream released. Threw it all away and now its as simple as installing Laravel Jetstream and fixing an issue a.k.a. building your SaaS. That's how we created https://thatswhy.app.

Full auth system.
Team support.
Invite support.
Email validation.

But something like this is of course only available for Laravel. If you use NodeJS or some other language you just need to hope someone has made it.

Would be cool if there was a solution that doesn't depend on a specific programming language or has integrations with all popular languages.

Definitely faced this also, I guess most devs build a boilerplate over time...

I think template/boilerplate is a good way to do this if you are constantly making projects like this. Saves a lot of time and let's you focus on important things. =)

Also there is https://sailsjs.com/ if you are working with node.

I built myself a boilerplate with expressjs+mongoose a while back to solve the problem for my own projects. It includes authentication, user management, email verification, password resets and access control stuff. It's pretty easy to expand and work with! I actually thought about improving it further and then selling it as a template.

Yeah, but I haven't found a good boilerplate for my needs: basically account management with high level company "umbrella" entity that owns the resources and social auth with github and gitlab, that works with Django and can be interacted with through an GraphQL API. Yeah I know, pretty specific.

I managed to get something working in a few days with django-allauth, but I had to basically convert all views that come with it into graphene mutations. And I am fighting the framework all the time (eg. the most annoying thing: you can't log in/connect as a user with both social media accounts at the same time. I had to hack my way around it).

I explored some already made solutions, such as auth0 (but I couldn't make gitlab login to work, absolute zero information online on how to configure it and it's impossible to debug, only the other way around, using auth0 to log in into gitlab) .

But yeah, at some point after I reach a stable state with this boilerplate functionality I'll create a boilerplate project for it.

That was the number 1 distraction point I always had when building products. I was always busy with setting up basic stuff like auth and project structure so that I never really thought about the product and the problem it solves.
I bought some boilerplates for different stacks and this problem is gone.
I just decide which stack is best for my product and can immediately start working on the core product. Game changer.
If you really care about building a solution and you don't want to hack around (what is completely okay too), I highly recommend getting a solid boilerplate.

Depends. If you want to use PHP, there are Laravel/Symfony/Wordpress that provides your bullet points out of the box? (Should be the same with other prog langs).

Myself kinda like copy paste code from previous project if needed.

Boilerplates like https://usegravity.app/ exist and are doing well.