SSO Setup
Configure Single Sign-On (SSO) for your organization using SAML 2.0 or OIDC. SSO lets your team sign in with their existing corporate identity provider, eliminating separate passwords and centralizing access control.
Supported protocols
| Protocol | Use Case | Common Providers |
|---|---|---|
| SAML 2.0 | Enterprise identity federation | Okta, Azure AD, OneLogin, PingFederate |
| OIDC | Modern token-based auth | Google Workspace, Auth0, Keycloak |
How SSO works with Clevername
When SSO is configured, org members sign in through your identity provider (IdP). Clevername receives a signed assertion or token, validates it, and creates or links the user account. Existing Clevername accounts with matching email addresses are automatically linked.
Open SSO settings
Navigate to Organization → Settings → SSO. Only org owners can configure SSO.
Choose a protocol
Select SAML 2.0 or OIDC depending on what your identity provider supports. SAML is the most common for enterprise environments. There is no generic OAuth 2.0 option.
Configure your identity provider
Clevername provides the values you need to enter in your IdP:
- ACS URL (SAML) or Redirect URI (OIDC) — where the IdP sends responses
- Entity ID (SAML) or Client ID (OIDC) — identifies Clevername to your IdP
- Metadata URL — for automatic configuration exchange
Enter IdP details in Clevername
Paste the details from your IdP into Clevername:
- SAML: IdP metadata URL or XML, IdP Entity ID, certificate
- OIDC: Issuer URL, Client ID, Client Secret
Save and, optionally, enforce
Click Save SSO Configuration. There is no test-connection button or active toggle; verify by signing in through the IdP login URL. The page notes that full SAML enforcement requires the Supabase Pro plan and stores your configuration so it is ready when that is in place. Optionally, enforce SSO for a verified email domain from the org settings page: users whose email is on that domain must then sign in through the IdP.