Supabase Adds Support for Custom OIDC Providers in Auth.

Supabase has expanded its authentication system with support for custom OpenID Connect (OIDC) providers, giving developers the ability to integrate virtually any identity provider into their projects rather than being limited to the platform's built-in options.

The addition was announced on LinkedIn alongside a blog post with full implementation details. Custom OIDC is a meaningful addition for teams building in regulated industries or enterprise environments where identity management is handled by existing corporate systems — think Okta, Auth0 custom tenants, Microsoft Entra with non-standard configurations, or bespoke internal identity servers.

OIDC, or OpenID Connect, is the standard protocol that sits on top of OAuth 2.0 and is used by virtually every modern identity provider to handle authentication. Until now, Supabase Auth supported a curated list of social and enterprise providers out of the box. Custom OIDC support changes that: developers can now point Supabase at any standards-compliant identity provider, provide the necessary configuration (issuer URL, client ID, client secret), and have it work like a native provider.

For teams that have existing user bases managed in separate identity systems, this removes a significant migration barrier. Rather than forcing users through a new sign-up flow, a product can simply federate with the existing IdP and inherit all user sessions and roles.

This is also relevant for multi-tenant SaaS products where each enterprise customer may run their own identity provider. Custom OIDC makes it possible to configure per-tenant authentication without maintaining separate infrastructure.

The no-code and low-code ecosystem has seen a surge in teams using Supabase as the backend for apps built in tools like Bubble, Webflow, and Lovable. For those teams, auth has historically been one of the stickier configuration challenges when enterprise clients come knocking with SSO requirements. Custom OIDC gives those builders a cleaner path to enterprise readiness without switching backend providers.

Supabase Auth already handles session management, row-level security integration, and JWT issuance. Adding a custom OIDC provider slots into that existing pipeline, so downstream permissions and data access policies don't need to change.

The feature is documented in the official Supabase blog and is available to configure through the project dashboard.