Menu
I've been having a hard time finding the SLA behind Google Firebase Authentication. According to Service Level Agreement for Hosting and Realtime Database, Firebase shall be available with a Monthly Uptime Percentage of at least 99.95%. Does it apply to the Authentication Services?
594
Firebase ID tokens are short lived and last for an hour; the refresh token can be used to retrieve new ID tokens. Refresh tokens expire only when one of the following occurs: The user is deleted. The user is disabled.
Because it IS slow and for this reason you should avoid using it. Build your own authentication, like I did and you'll discover how significantly faster it is.
Definitions "Monthly Uptime Percentage" is calculated by subtracting from 100% the percentage of continuous 5 minute periods of Downtime during the month. Percentage measurements exclude downtime resulting directly or indirectly from any Firebase SLA Exclusion (defined below).
Firebase Authentication provides backend services, easy-to-use SDKs, and ready-made UI libraries to authenticate users to your app. It supports authentication using passwords, phone numbers, popular federated identity providers like Google, Facebook and Twitter, and more.
Here is what I got from Google Support when I asked about the differences between Firebase Auth and Cloud Identity Platform.
The reason for the pricing difference between Firebase Auth and Cloud Identity Platform is Cloud Identity Platform offers a SLA of 99.95% while Firebase Auth has no SLA.
They also mentioned other reasons (ex: SAML and Multitenancy) which is unrelated to your question.
197
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
