Firebase Connector

You can integrate Descope with Firebase to continue using Firebase's services while replacing its authentication system with Descope Flows. This is especially useful if your application is already built on Firebase but you want to take advantage of Descope’s flexible and secure authentication experience.

With this integration, Descope can return a Firebase-compatible token as part of the authentication response—available through our SDKs or API.

Configuring the Firebase Connector

Find the Firebase connector on the Connectors page of the Descope Console.

• Connector Name: Provide a unique name for your connector. This assists in distinguishing it, especially when multiple connectors are derived from the same template.
• Connector Description: Briefly explain the purpose of this connector.
• Service Account: This is the JSON data for your Firebase project's service account. Read below on how to find this.

Getting the Service Account JSON

1. In Firebase, navigate to the Project Settings for your project by clicking the gear in the top left of the Console after selecting your project.

2. Click on the Service Accounts tab.

3. Press the Generate new private key button to download the JSON data.

4. Open the JSON file and copy the entire file (including the brackets) into the Service Account section of the connector configuration.

5. The connector is now configured, you can test it like above by pressing the Test button to ensure the Service Account was added correctly.

Enabling the Connector

Now that the connector is configured, it can be enabled through the External Token section of your Descope project's Settings. Read more on external tokens to enable Firebase tokens in your flows.

The external token generated by Firebase will be included in the authentication response at the end of your flows.