Similar Posts

Subscribe
Notify of
1 Answer
Oldest
Newest Most Voted
Inline Feedbacks
View all comments
tide1109
1 year ago

SAML and OpenID Connect (OIDC) are standards for authenticating users. OpenID Connect is aud OAuth2.

The buttons like “Login with Google” are a practical example for OpenID Connect. After the “Login with Google” you will be forwarded to Google. There you will log in with Google if not done. If you have confirmed the link, you will be forwarded to e.g. good question. The website receives a JSON Webtoken (JWT) with a few information about the name, e-mail and possibly permissions. The password is not known to the website. Also not encrypted.

In summary, it is also known as Single Sign-on (SSO).

If you are interested in more details, you will find some results on the Internet with the technical terms.

As Google (Firebase belongs to Google) makes pricing, I cannot tell you from my own experience. I set up a Keycloak server with OpenID Connect connection myself.

I did not read it directly, but I can introduce myself to Firebase Identify and Google Login:

Login via Google seems to be free for at least 12 projects.

With Identiy Platform, I could imagine that there is a very own user database. Then it would not be login with Google, but login with XY. As in principle as I have run Keycloak locally, only with Google’s software on their servers with their support.

When it comes to cost, you must always distinguish between end users and companies. For end users a lot is free, but companies pay for it.

The 50k are MAU (monthly active user), so monthly active users. Google defines it like this:

An active user is anyone who uses his account within the billing period.

Source