---
slug: custom-oidc-third-party-auth
published: 2026-11-17
change_type: new-feature
affected_products:
  - Studio
  - Auth
page: https://supabase.com/changelog/custom-oidc-third-party-auth
---

# Add custom OIDC providers for third-party auth from the Dashboard

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

1. Open **Authentication** > **Third-Party Auth** and select **Add provider** > **Custom OIDC**.
2. Enter your provider's issuer URL. Its signing keys must be available at the issuer's `/.well-known/openid-configuration`.
3. 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](https://supabase.com/docs/guides/auth/third-party/custom-oidc) for the Management API option, the `role` claim, client setup, and RLS policies.
