Enterprise SSO for Supabase Auth Without Migrating Users
Blog post from SSOJet
Supabase’s native SAML SSO, available on Pro plans and above, supports domain-based SAML sign-in but requires engineers to configure each customer identity provider through the CLI, lacks traditional IdP-initiated and single-logout support, does not link SAML identities to existing same-email accounts, and charges beyond included SSO monthly active users. As an alternative enabled by Supabase’s April 2026 support for custom OIDC providers, a single external SSO layer such as SSOJet can sit between Supabase and multiple customer SAML or OIDC providers, routing users by email domain while preserving existing Supabase users, sessions, RLS policies, and application integrations. This approach can link OAuth identities to existing users, but requires safeguards including verified tenant domains, enforced SSO for enrolled domains, tenant claims added to JWTs through a custom access-token hook, and RLS policies that use those claims rather than email domains alone. For deprovisioning, SCIM events from the SSO layer can trigger webhook-based bans in Supabase, although short token lifetimes or additional RLS checks may be needed to limit access from already-issued tokens. Native SAML may suit a small number of SAML-only customers, while a custom OIDC gateway is presented as better suited to multi-tenant applications needing scalable customer-managed setup, OIDC compatibility, identity linking, and SCIM-based offboarding.
| Trend | Post Mentions | Total Month Mentions | Posts | Companies | MoM |
|---|---|---|---|---|---|
| Platform Engineering | 22 | 1,145 | 237 | 66 | -43% |
| Edge Computing | 1 | 38 | 20 | 11 | -80% |
Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.