Index of every page on this site: llms.txt
All skills
firebase avatar

/firebase-auth-basics

@99954a3 official
by firebasefirebase/agent-skills520 stars
116
Run it yourself

Guide for setting up and using Firebase Authentication. Use this skill when the user's app requires user sign-in, user management, or secure data access using auth rules.

Use this Skill: https://skilld.dev/gh/firebase/agent-skills/firebase-auth-basics

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈48 tokens for metadata: the name and description. ≈1.1k when used: this file. ≈5.8k more on demand in 5 files.

Description uses 2.4% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈193 characters, or 2.4%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Prerequisites

  • Firebase Project: Created via npx -y firebase-tools@latest projects:create (see firebase-basics).
  • Firebase CLI: Installed and logged in (see firebase-basics).

Core Concepts

Firebase Authentication provides backend services, easy-to-use SDKs, and ready-made UI libraries to authenticate users to your app.

Users

A user is an entity that can sign in to your app. Each user is identified by a unique ID (uid) which is guaranteed to be unique across all providers. User properties include:

  • uid: Unique identifier.
  • email: User's email address (if available).
  • displayName: User's display name (if available).
  • photoURL: URL to user's photo (if available).
  • emailVerified: Boolean indicating if the email is verified.

Identity Providers

Firebase Auth supports multiple ways to sign in:

  • Email/Password: Basic email and password authentication.
  • Federated Identity Providers: Google, Facebook, Twitter, GitHub, Microsoft, Apple, etc.
  • Phone Number: SMS-based authentication.
  • Anonymous: Temporary guest accounts that can be linked to permanent accounts later.
  • Custom Auth: Integrate with your existing auth system.

Google Sign In is recommended as a good and secure default provider.

Tokens

When a user signs in, they receive an ID Token (JWT). This token is used to identify the user when making requests to Firebase services (Realtime Database, Cloud Storage, Firestore) or your own backend.

  • ID Token: Short-lived (1 hour), verifies identity.
  • Refresh Token: Long-lived, used to get new ID tokens.

Workflow

1. Provisioning

Option 1. Enabling Authentication via CLI

Only Google Sign In, anonymous auth, and email/password auth can be enabled via CLI. For other providers, use the Firebase Console.

Configure Firebase Authentication in firebase.json by adding an 'auth' block:

{
  "auth": {
    "providers": {
      "anonymous": true,
      "emailPassword": true,
      "googleSignIn": {
        "oAuthBrandDisplayName": "Your Brand Name",
        "supportEmail": "support@example.com",
        "authorizedRedirectUris": [
          "https://my-project-id.firebaseapp.com/__/auth/handler",
          "http://localhost"
        ]
      }
    }
  }
}

[!NOTE] If the Google Sign-In popup opens and immediately closes with the error [firebase_auth/unauthorized-domain], it means the domain is not authorized. For local development, add http://localhost to authorizedRedirectUris in firebase.json (or ensure localhost is included in the Authorized Domains list in the Firebase Console under Authentication > Settings > Authorized domains). CRITICAL: Do NOT include the port number in authorizedRedirectUris (e.g., use http://localhost, NOT http://localhost:9090 or http://localhost:4000), and do NOT include the protocol or port number in the Console Authorized Domains list (use localhost). Including a port number in authorizedRedirectUris causes firebase deploy --only auth to fail with INVALID_AUTHORIZED_DOMAIN.

CRITICAL: After configuring firebase.json, you MUST deploy the auth configuration to the Firebase backend for the changes to take effect. This is essential for auth providers like Google Sign-In, email/password, etc. to auto-generate the necessary OAuth clients for your app platforms. Run:

npx -y firebase-tools@latest deploy --only auth
Option 2. Enabling Authentication in Console

Enable other providers in the Firebase Console.

  1. Go to the https://console.firebase.google.com/project/_/authentication/providers
  2. Select your project.
  3. Enable the desired Sign-in providers (e.g., Email/Password, Google).

2. Client Setup & Usage

Web See references/client_sdk_web.md.

Flutter See references/flutter_setup.md. Android (Kotlin) See references/client_sdk_android.md.

iOS (Swift) See references/ios_setup.md.

3. Security Rules

Secure your data using request.auth in Firestore/Storage rules.

See references/security_rules.md.

Source: SKILL.md on GitHub

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

1 warning1mo5 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    The skill provides comprehensive and safe documentation for integrating Firebase Authentication into web, Android, iOS, and Flutter applications. It utilizes official Firebase CLI tools and Google Maven repositories for version management, following standard vendor practices.

  • Socket1mo

    No alerts

  • Snyk1mo

    Risk: MEDIUM · 1 issue

  • Runlayer8mo

    3 files scanned · No issues

  • ZeroLeaks7mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 99954a3. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Activeupdated 2 months ago
metadata
{
  "author": "Google LLC",
  "category": "Identity"
}
Other metadata
compatibility
This skill is best used with the Firebase CLI, but does not require it. Firebase CLI can be accessed through `npx -y firebase-tools@latest`.
  • Auth
  • firebase
  • authentication
  • web
  • flutter
  • android
  • oauth
  • jwt
  • firestore
  • security-rules

README badge

README badge for firebase/agent-skills/firebase-auth-basics

Provides guidance for setting up Firebase Authentication, including user management, identity providers (email/password, Google Sign-In, phone, anonymous, custom), token handling, and security rules. Use this when building sign-in flows or securing data access with auth rules in Firebase projects.

Generated from the current SKILL.md.

Does this skill require the Firebase CLI?
No, but it is recommended. The Firebase CLI can be accessed via `npx -y firebase-tools@latest` and is needed to deploy auth configuration changes.
Which identity providers can be enabled via CLI?
Only Google Sign In, anonymous auth, and email/password auth can be configured through the CLI. Other providers (Facebook, Twitter, GitHub, etc.) must be enabled in the Firebase Console.
What do I do if Google Sign-In returns an 'unauthorized-domain' error?
The domain must be added to the Authorized Domains list. For local development, add `localhost` (without protocol or port) to the list in the Firebase Console or via the `authorizedDomains` field in `firebase.json`.
Does this skill cover all platforms?
The skill includes references for Web, Flutter, and Android (Kotlin) client setup, but the core guide focuses on configuration and concepts. Platform-specific implementation details are in separate reference files.
What happens after I configure firebase.json with auth settings?
You must run `npx -y firebase-tools@latest deploy --only auth` to deploy the configuration to Firebase and auto-generate the necessary OAuth clients for your app.

Generated from the current SKILL.md. These answers refresh after source changes.