The Third-Party Auth page in the Dashboard now supports custom OIDC providers, in addition to Firebase, Clerk, WorkOS, Auth0, and Amazon Cognito.
What's new
- A Custom OIDC option in the Add provider menu on the Third-Party Auth page. Enter the issuer URL and Supabase registers it for your project.
- Issuer URLs must use
https://and can't include a query string, fragment, or credentials. The Dashboard shows an inline error for invalid values. - Custom issuers already registered through the Management API now appear in the provider list, labeled Custom OIDC with their issuer URL. You can delete them from the Dashboard.
How to use it
- Open Authentication > Third-Party Auth and select Add provider > Custom OIDC.
- Enter your provider's issuer URL. Its signing keys must be available at the issuer's
/.well-known/openid-configuration. - Select Add provider. Supabase then accepts JWTs signed by that issuer.
The Dashboard doesn't yet support custom JWKS URLs or inline JWKS. Use the Management API for those.
See the custom OIDC guide for the Management API option, the role claim, client setup, and RLS policies.