←back to thread

282 points bundie | 3 comments | | HN request time: 3.76s | source
Show context
exiguus ◴[] No.44382638[source]
If i get it correctly, it solves the problem, to store data on MVP/Prototype Auth providers like Superbase, Auth0 or Firebase.

How does it compare to something mature like keycloak?

And what is the difference to just self-host superbase?

replies(1): >>44383160 #
Spivak ◴[] No.44383160[source]
The killer feature is that it's embeddable into your app. You don't have to host anything besides your app and your app's database.

I can't understand why people who aren't Google scale do it any other way. When you're at the point where you need a separate auth service I'd call that good problems to have.

replies(3): >>44383741 #>>44385837 #>>44389066 #
1. uh_uh ◴[] No.44385837[source]
Does it also embed two-factor authentication, confirmation/reset emails for me? Those are the reasons one might want to go with Firebase.
replies(2): >>44386813 #>>44386902 #
2. trollbridge ◴[] No.44386813[source]
Another reason to use Firebase is because they can provide a lot the advanced security (e.g. blacklists for 2FA phone numbers/emails coming from an algorthm whose innards are only known to Google).
3. notpushkin ◴[] No.44386902[source]
It does 2FA. You have to implement emails yourself, but honestly it’s not that big of a deal (you likely have to do other emails for your app anyway).

It also does a bunch of other auth things, like OIDC.