Firebase
for LuumenAI
Check Firebase Authentication config and sign-in flows from the terminal
Connect Firebase Authentication with a Web API key and Luumen can read the public auth config for the project, see which sign-in methods an account has used, and validate a password-reset code before anyone touches the account. Sign-in and token exchange calls run as previewed steps you approve, so support work leaves a record.
The Firebase toolbox
8 tools: 3 read, 5 write. Reads answer instantly. Writes require approval by default. Everything is logged.
- ReadDiscover Sign-In MethodsLook up sign-in methods previously used by a Firebase account email.
- ReadGet Auth Project ConfigGet the public Firebase Authentication configuration associated with the connected Web API key, including the project ID and authorized domains.
- ReadVerify Password Reset CodeValidate a Firebase password-reset OOB code and identify the associated email and request type without changing the password.
- WriteRefresh ID TokenExchange a Firebase refresh token for a fresh Firebase ID token and rotated refresh token using Google's Secure Token service. Approval by default
- WriteSign In With Custom TokenExchange a trusted server-minted Firebase custom token for a Firebase ID token and refresh token. Approval by default
- WriteSign In With Email LinkComplete Firebase email-link sign-in using an email address and the one-time OOB code from a previously delivered sign-in link. Approval by default
- WriteSign In With Identity ProviderSign in with one configured external identity provider using provider-specific OAuth or OIDC credential parameters. Approval by default
- WriteSign In With PasswordSign in an existing Firebase Authentication user with email and password and return fresh ID and refresh tokens. Approval by default
One prompt, start to finish
What a governed Firebase run looks like inside Luumen.
Questions
Authorize once with API token. Luumen lists the scopes each action needs before you approve the connection, and credentials never appear in the chat.
This connection exposes write actions such as refresh id token, sign in with custom token, sign in with email link, sign in with identity provider, and more. For connected tools, admins configure which actions may run automatically and which require approval, within the access granted to the user. Review the configured approval policy before enabling write access.
You decide. Actions are granted per agent, skill, and team, and per environment — production is not staging. Read access can be broad while writes stay narrow.
Every call to Firebase — read or write, approved or declined — is recorded with the actor, the input, and the result, and can be linked to the ticket or change record.
Often connected alongside
All integrations
OktaAccess and posture from Okta, with approval on every change.
Microsoft Entra IDAccess and posture from Microsoft Entra ID, with approval on every change.
Auth0Access and posture from Auth0, with approval on every change.Ping IdentityAccess and posture from Ping Identity, with approval on every change.Put Firebase to work with Luumen
Connect in minutes. Every action scoped, approved, and audited from day one.