From the source
But what about your company's SAML-to-OIDC bridge?
A regional identity provider required for compliance?
Your self-hosted GitHub Enterprise?
Until now, if your identity provider wasn't on the built-in list, you were stuck.
Today we're launching Custom OIDC Providers , letting you connect any standards-compliant OpenID Connect identity provider to your Supabase project.
Once configured, custom providers work just like built-in ones: same sign-in flow, same client libraries, same RLS enforcement.
Why We Built This # Built-in providers cover the most common cases, but not every identity provider fits neatly into that list: Regional compliance : Government or industry-specific providers mandated in certain regions.
Self-hosted providers : GitHub Enterprise Server, GitLab self-managed, or any on-premise OAuth2 service.
Niche providers : Gaming platforms, healthcare identity networks, or industry-specific SSO systems.
Last year, we shipped OAuth 2.1 server capabilities so your Supabase project can be an identity provider.
…
