neetcode22

100% agree with you. I've gone through the entire journey of experimenting + building my own authentication to using a reliable open source solution.

Been using this passwordless login recipe by supertokens for my recent projects: https://supertokens.com/docs/passwordless/introduction

Re-inventing the wheel calls for a lot more than usually anticipated. Best to keep it simple - and if you do end up innovating might as well open source it or contribute to an already popular OS solution.

I found this blog on session management really useful: https://supertokens.com/blog/all-you-need-to-know-about-user...

Oh i see :) Good luck, man! Keep building. Will follow your repo

You could use ShowHN in the title for wider reach. Also, checkout: https://github.com/supertokens/ (might help with building MFA and for building a couple of other auth solutions)

Wow, you built all of this by yourself? Looks really good!

Also, have you heard of Supabase?

I am also interested in learning how you built your auth solution - like built from scratch or made using OS SDKs?

Since you've contributed to Keycloack, you might find this OS project interesting: https://github.com/supertokens/supertokens-core

The core is built using Java (like Keycloak)and it's easier to use

This looks really good!

What solution are you using for authentication and authorisation?

I think it depends entirely on your use case. If the user isn't storing a lot of info in your app then passwordless is the way to go.

Also, important to recognise that replacing a password with a different single factor does not enable passwordless as used by most enterprise companies. Passwordless implies two factor, with both factors not including a password.