Loading

Spiff: SSO Domain Setup

Date de publication: Aug 11, 2026
Description

Spiff supports configuring Single Sign-On (SSO) based on email domains by specifying one or more domain names in the Admin tab under Settings > Security > SSO Email Domains. To enforce SSO for users with emails in specified domains, enter those domains in the list without the "@" symbol. Users with emails outside these domains cannot log in via SSO and will need to log in with their email and password.

Résolution

This article explains how to set up or update Single Sign-On (SSO) domain configuration in Spiff, including uploading your identity provider's SAML (Security Assertion Markup Language) file and understanding how Spiff handles multiple domains.

Steps to Set Up SSO Email Domains

  1. Log in to your Spiff instance as an Admin.
  2. Navigate to the Admin tab in the main menu.
  3. Click on Settings.
  4. Select the Security section from the Settings menu.
  5. Locate the SSO Email Domains field.
    1. Enter the email domain(s) you want to enforce SSO for, e.g., example.com.
    2. Do not include the "@" symbol.
  6. In the SAML Settings section, click Upload.
  7. Select the SAML XML file you have downloaded from your identity provider (Google Workspace, Okta, Microsoft Azure AD, etc.).
  8. Ensure the XML file contains the required SAML configuration details.
  9. Click Save to apply the configuration. This activates SSO authentication for users with email addresses matching the specified domains.
  10. To update or add a new domain later, repeat these steps and include the new domain in the SSO Email Domains field.
  11. Update this setting before or promptly after any email domain changes to avoid login issues.

Example Scenario

Suppose your company uses Google Workspace for identity management, and you want users with email addresses ending in @example.com to log in using SSO. You'd enter example.com in the SSO Email Domains section, then upload the SAML XML file provided by Google Workspace to configure the authentication flow.

  • Any user with an email ending in @example.com will be required to authenticate via SSO.
  • Users with other email addresses, such as @gmail.com or @xyz.com, will be required to log in using the Spiff username and password method.

Considerations - No Redirect URL in XML

If the SAML XML file doesn't specify a redirect URL but includes a POST URL, Spiff will default to using the POST URL as the redirect URL. However, Spiff does not support POST-based authentication directly, so ensure the XML file from your identity provider is properly configured to prevent any issues.

Multiple Domains

  • If you want to enforce SSO for users across multiple domains, you must enter all relevant domains in the SSO Email Domains field.
  • Make sure your identity provider can support multiple domains under one configuration if required.
  • Only one SAML configuration can be enabled at a time with multiple domains.
  • Domains entered into the configuration are not case-sensitive.

By following these steps and guidelines, you can ensure that your users are securely authenticated via SSO based on their email domains, improving the security and user experience within Spiff.

Numéro d’article de la base de connaissances

005227026

 
Chargement
Salesforce Help | Article