# Supabase — Custom OIDC Providers for Supabase Auth

- Company: Supabase (supabase.com)
- Announced: 2026-04-08
- Category: not stated
- Coverage: not counted
- Announcement: yes
- Group: announcements
- Source: https://supabase.com/blog/custom-oauth-oidc-providers
- Record: https://forck.live/items/21294-custom-oidc-providers-for-supabase-auth
- Subject: Supabase

Supabase Auth ships with over 20 built-in social providers: Google, GitHub, Apple, and more. 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. …

---

Record: https://forck.live/items/21294-custom-oidc-providers-for-supabase-auth
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md