SSO is available on Enterprise plans only. Contact sales to upgrade.
Supported Providers
EngageFabric supports two SSO protocols:SAML 2.0
Industry standard for enterprise SSO. Works with Okta, Azure AD, OneLogin, and more.
OpenID Connect
Modern OAuth 2.0-based protocol. Works with Google Workspace, Auth0, Keycloak, and more.
Setting Up SAML SSO
Step 1: Get Your Service Provider Details
First, retrieve your SAML metadata from the API:Step 2: Configure Your Identity Provider
Add EngageFabric as a new application in your IdP:- Okta
- Azure AD
- OneLogin
- Go to Applications > Create App Integration
- Select SAML 2.0
- Enter the following settings:
- Single Sign-On URL:
{acsUrl from above} - Audience URI (SP Entity ID):
{entityId from above} - Name ID Format: EmailAddress
- Single Sign-On URL:
- Under Attribute Statements, add:
email→user.emailfirstName→user.firstNamelastName→user.lastName
- Save and copy the Metadata URL or download the IdP metadata
Step 3: Configure EngageFabric
Update your SSO configuration with the IdP details:Setting Up OIDC SSO
Step 1: Create an OAuth Application
In your identity provider, create a new OAuth/OIDC application:- Google Workspace
- Auth0
- Keycloak
- Go to Google Cloud Console
- Navigate to APIs & Services > Credentials
- Click Create Credentials > OAuth client ID
- Select Web application
- Add redirect URI:
https://api.engagefabric.com/api/v1/auth/sso/your-org/callback - Copy the Client ID and Client Secret
Step 2: Configure EngageFabric
Configuration Options
| Field | Type | Description |
|---|---|---|
provider | string | SAML or OIDC |
displayName | string | Friendly name shown on login button |
autoProvision | boolean | Auto-create users on first login |
defaultRole | string | Role for auto-provisioned users |
allowedDomains | array | Restrict to specific email domains |
SAML-Specific Fields
| Field | Description |
|---|---|
samlEntityId | IdP Entity ID from metadata |
samlSsoUrl | IdP SSO endpoint URL |
samlCertificate | IdP X.509 certificate |
OIDC-Specific Fields
| Field | Description |
|---|---|
oidcIssuer | IdP issuer URL (e.g., https://accounts.google.com) |
oidcClientId | OAuth client ID |
oidcClientSecret | OAuth client secret |
oidcScopes | Requested scopes (default: openid, profile, email) |
Testing Your Configuration
Before enforcing SSO, test that it works correctly:loginUrl in a browser to test the full SSO flow.
Auto-Provisioning
WhenautoProvision is enabled:
- New users are automatically created on first SSO login
- They’re assigned the
defaultRoleyou specified - Their name and email are populated from the IdP
- They don’t need a separate invitation
Domain Restrictions
UseallowedDomains to restrict which email domains can authenticate:
Disabling SSO
To disable SSO and revert to password authentication:API Reference
| Method | Endpoint | Description |
|---|---|---|
| GET | /v1/enterprise/sso | Get current SSO configuration |
| PUT | /v1/enterprise/sso | Create or update SSO configuration |
| DELETE | /v1/enterprise/sso | Disable SSO |
| POST | /v1/enterprise/sso/test | Test SSO configuration |
| GET | /v1/enterprise/sso/metadata | Get SAML metadata for IdP setup |
Troubleshooting
SSO login fails with 'Invalid signature'
SSO login fails with 'Invalid signature'
Ensure you’ve copied the complete IdP certificate, including the
-----BEGIN CERTIFICATE----- and -----END CERTIFICATE----- lines.Users are not being auto-provisioned
Users are not being auto-provisioned
Check that:
autoProvisionis set totrue- The user’s email domain is in
allowedDomains(if set) - You haven’t reached your plan’s team member limit
OIDC fails with 'Invalid redirect URI'
OIDC fails with 'Invalid redirect URI'
Ensure the callback URL in your IdP exactly matches:
https://api.engagefabric.com/api/v1/auth/sso/{your-org-slug}/callback