Authentication Options in SnapApp
on 07-17-2024 12:00 AM by SnapApp by BlueVector AI
51
SnapApp uses Firebase Authentication to provide a secure and seamless user experience. Users can register and authenticate using various methods. This document outlines the different authentication options available in SnapApp. SnapApp does not store any user credentials, instead it uses Firebase Authentication to securely store and manage user credentials.
Native Providers
| Provider | Description |
|---|---|
| Email and Password | Users can register and authenticate using their email and password. Passwordless login is also available and must be configured in Firebase. |
| Phone | Users can register and authenticate using their phone number. |
| Anonymous | You can use Firebase Authentication to create and use temporary anonymous accounts to authenticate with Firebase. |
Note: When using passwordless login, a verification email will be sent to the provided email address.
Additional Providers
Note: All of the providers listed below must be enabled and configured in the Firebase Console.
| Provider | Description |
|---|---|
| Users can register and authenticate using their Google account. | |
| Users can register and authenticate using their Facebook account. | |
| Users can register and authenticate using their Twitter account. | |
| GitHub | Users can register and authenticate using their GitHub account. |
| Microsoft | Users can register and authenticate using their Microsoft account. |
| Apple | Users can register and authenticate using their Apple account. |
| Yahoo | Users can register and authenticate using their Yahoo account. |
Custom Providers
Note: To use the custom providers listed below, you need to upgrade to Firebase Authentication with Identity Platform.
| Provider | Description |
|---|---|
| SAML | Users can register and authenticate using Security Assertion Markup Language (SAML). |
| OpenID Connect | Users can register and authenticate using OpenID Connect. |
SAML and OpenID Connect can be used to integrate with your existing Single Sign-On (SSO) solution such as Okta, OneLogin, or Azure Active Directory (AD).
