Firebase Auth + SAML and OIDC Without Migrating Users
Blog post from SSOJet
Firebase supports native SAML and OpenID Connect only after upgrading to Firebase Authentication with Identity Platform, which changes provider management, billing, and usage limits while introducing features such as MFA, multi-tenancy, and blocking functions. Native SSO can create account-linking complications for existing users because Firebase UIDs often anchor Firestore data, Storage paths, and security rules; depending on email-account settings, users may encounter credential conflicts or receive duplicate accounts that require manual merging. An alternative is to retain standard Firebase Authentication and use an external SSO layer to handle each customer’s SAML or OIDC connection, then complete an OIDC authorization-code flow on the backend and issue a Firebase custom token for the user’s existing UID. This approach preserves existing application data and permissions, but depends on secure identity mapping: email matching should be limited to verified customer domains, and the external identity provider’s stable subject identifier should be stored against the Firebase UID to prevent account takeover or unintended reassignment after email changes. Native Identity Platform SSO may suit organizations with few known providers and a need for its additional capabilities, while the custom-token model can be more flexible for B2B applications supporting many customer-managed identity providers.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Platform Engineering | 14 | 1,145 | 237 | 66 | -43% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.