Google Workspace Legacy SAML Integration Guide

Suggest an edit

Prerequisites

  • Super Administrator access to the Google Admin Console
  • A SplitSecure Identity Provider created and approved
  • The Security settings administrator privilege in Google Workspace
  • A separate browser or browser profile with SplitSecure configured (for testing)

Google Workspace Configuration

1 Add a New Identity Provider

  1. Log in to the Google Admin Console
  2. Navigate to Security → Authentication → Single sign-on (SSO) with third-party identity providers (IDPs)

2 Access Legacy SSO Profile Settings

  1. In the Third-party SSO profiles section, click Add SAML profile
  2. At the bottom of the IdP details page, click Go to legacy SSO profile settings
  3. Check the Enable SSO with third-party identity provider box

3 Configure IdP Details

Gather the following values from SplitSecure before proceeding:

  1. In SplitSecure, go to Secure Accounts → SAML2 Identity Providers
  2. Click Details on the desired identity provider
  3. Note the values below and download the certificate
Field Value Notes
Sign-in page URL https://app.splitsecure.com/saml2/sp/login SplitSecure SSO endpoint (must use HTTPS)
Sign-out page URL https://app.splitsecure.com/saml2/sp/logout SplitSecure logout endpoint (must use HTTPS)
Certificate (Upload X.509 certificate) Download from SplitSecure: Secure Accounts → SAML2 Identity Providers → [Your IdP] → Details → Download Certificate
Change password URL https://app.splitsecure.com/saml2/sp/password-change Where users go to reset their password
  1. Click Upload certificate to upload the X.509 certificate from SplitSecure
  2. Check Use a domain specific issuer
  3. Click Save

The Legacy SSO profile will appear in the SSO profiles table.

4 Assign the SSO Profile to Users

  1. Navigate to Security → Authentication → SSO with third party IdP
  2. Click Manage SSO profile assignments
  3. Click Get started (first time) or Manage assignments
  4. Select the organizational unit or group to assign
  5. Under SSO profile assignment, choose Another SSO profile
  6. Select your newly created SplitSecure SAML profile from the dropdown
  7. Click Save

5 Create Administrator Account

  1. Navigate to Directory → Users
  2. Click Add new user
  3. Create a user, then click the newly created user
  4. Click Change organizational unit and add the user in the same Organizational unit selected in Step 4
  5. Click Admin roles and privileges and add Services Administrator

6 Configure Domain-specific Service URLs

  1. Navigate to Security → Authentication → Single sign-on (SSO) with third-party identity providers (IDPs)
  2. Click Domain-specific Service URLs
  3. Select Require users to enter their username on Google’s sign-in page first

SplitSecure Configuration

1 Create the Google Workspace Legacy Secure Account

  1. In SplitSecure, navigate to Secure Accounts → Create Account → Google Workspace Legacy
  2. Enter a name for your account
  3. Select the Identity Provider used in the Google Workspace configuration
  4. Enter the domain with your organization’s primary Google Workspace domain
  5. (Optional) Provide a default email address that will be proposed when prompted to authenticate

Test Authentication

1 Test Authentication (SP-Initiated)

  1. Navigate to a Google Workspace service (e.g., mail.google.com)
  2. Enter a user email address from your Google Workspace domain
  3. You should be redirected to SplitSecure for authentication
  4. Enter your email address when prompted
  5. Click Request Access
  6. Complete the authentication flow

Troubleshooting

Issue Possible Cause Solution
User not redirected to IdP SSO not enabled Verify “Enable SSO with third-party identity provider” is checked
SAML assertion invalid Certificate mismatch Re-download the certificate from SplitSecure and re-upload to Google
User receives “Account not found” Email mismatch Ensure the SAML assertion email matches the Google Workspace email exactly
Entity ID mismatch error Domain-specific issuer mismatch Ensure SplitSecure Entity ID matches your domain-specific issuer setting
Super admin cannot use SSO Expected behavior Super administrators bypass SSO by default for security

External Resources