Search the documentation
Search the documentation...
SplitSecure documentation

On this page

Procedure · 8 steps

Google Workspace (Legacy)

Sign in to Google Workspace through SplitSecure with the legacy SSO profile, with an admin user that signs in only when your Guardian Team approves.

Updated

Before you start

  • Super Administrator access to the Google Admin console (opens in a new tab), or an admin role with the Security settings privilege.
  • A SplitSecure identity provider, created in a threshold vault and approved by its Guardian Team. See Create an identity provider.

  • A second browser profile, signed in to the Web App, for the test sign-in. Start and finish the test in that same profile.

This guide makes Google Workspace a connected app of your SplitSecure identity provider through Google’s legacy SSO (single sign-on) profile, so an admin user signs in only when your Guardian Team, the group of devices that together approve each proposal, approves it. The legacy profile uses a domain-specific issuer, which the Web App derives from your Google domain.

Values you exchange

Value Where to find it Where to paste it
SSO URL (HTTP-Redirect) The identity provider’s SAML endpoints card in the Web App Google, Sign-in page URL, in Configure the legacy SSO profile
Signing certificate (PEM) The same card, Download Certificate → PEM format Google, Upload certificate, in the same step
Primary Google domain Your Google Workspace account, for example acme.com The Web App, Domain Name, in Create the connected app

Add SplitSecure as the legacy SSO profile in Google

In the Google Admin console

  1. Go to Security → Authentication → SSO with third party IdP.
  2. In Third-party SSO profiles, click Add SAML profile.
  3. At the bottom of the page, click Legacy SSO profile.
  4. Check Enable legacy SSO profile.

Open the Web App in another tab to copy the values.

In the Web App, open Vaults, then your vault, then the identity provider. The SAML endpoints card shows three values:

  • SAML IdP Entity ID
  • SSO URL (HTTP-Redirect)
  • SSO URL (HTTP-Post)

Under them, Download metadata XML saves the metadata file and Download Certificate offers the certificate in PEM format or DER format.

Field Value
Sign-in page URL The SSO URL (HTTP-Redirect)From the SAML endpoints card, not the SSO URL (HTTP-Post)
Sign-out page URL The SSO URL (HTTP-Redirect), ending in /logout instead of /login Opens after a user signs out of Google
Upload certificate The certificate fileDownload Certificate → PEM format on the card
Use a domain specific issuer CheckedGoogle then sends google.com/a/<your domain>, the issuer the connected app expects

Click Save. The legacy SSO profile appears in the SSO profiles table.

  1. Go to Security → Authentication → SSO with third party IdP.
  2. Click Domain-specific Service URLs.
  3. Select Require users to enter their username on Google’s sign-in page first.
  1. In SSO with third party IdP, click Manage SSO profile assignments.
  2. Click Get started the first time, or Manage assignments later.
  3. Select the organizational unit or group that signs in through SplitSecure.
  4. Under SSO profile assignment, choose Another SSO profile.
  5. Select the legacy SSO profile.
  6. Click Save.
  1. Go to Directory → Users.
  2. Click Add new user, fill in the user and save it.
  3. Open the new user and click Change organizational unit.
  4. Move the user to the organizational unit you selected in Assign the profile to users.
  5. Open Admin roles and privileges and assign Services Administrator.

Connect Google Workspace to SplitSecure

In the Web App

In the Web App, open Vaults, then your vault, then the identity provider. Click New Connected App and pick the service provider’s card. Name is required, and the Threshold Identity Provider field is fixed to this provider.

  1. Click the Google Workspace Legacy (SAML2) card.

  2. Enter a Name, for example Google Workspace.

  3. Set the NameID. Google matches each user by the email in the NameID, so the email SplitSecure sends must equal the user’s Google Workspace email. Keep NameID format on Email Address.

    Keep the default NameID value, Built from each person’s email. Its NameID template is ${user.email}, which SplitSecure fills with the email of the person who signs in. To accept only one email domain, enter it in Email must end with, for example @example.com. SplitSecure then refuses anyone whose email ends otherwise.

  4. In Domain Name, enter your primary Google Workspace domain, for example acme.com. The Web App also sets Email must end with to @acme.com.

  5. Optionally, under Advanced Options, turn on Selective notifications so members can choose who gets notified for the Guardian Team’s proposals, set the Account Sensitivity banner shown on this connected app’s proposals (None, Low, Medium, High or Critical), and enter a Description or a Reason for creation.

  6. Click Propose connected app. The Web App opens the proposal under Requests. The members of the Guardian Team approve it on their devices, in the mobile app. When the vote passes, the connected app appears under Connected Apps.

Test the sign-in

In the Web App

In the Web App, open Connected Apps, find the new connected app and click Log in. Some service providers, such as Iru, accept only a sign-in that starts on their side. For those, the Web App first sends you to the service provider, which sends you back. The Web App then shows the details of the connected app. If the page asks for a value, such as a NameID, enter it. To leave a note for the approvers, open Advanced Options and fill in Reason for access. Click Log in again. The members of the Guardian Team approve the sign-in on their devices, in the mobile app. When the vote passes, click Login on the proposal page to finish the sign-in at the service provider.

In the access form, enter the admin user’s Email.

  1. In the test profile, open a Google service, for example https://mail.google.com.
  2. Enter the admin user’s email.
  3. The service provider sends you to the Web App, which opens the Log in page for the connected app. If the page asks for a value, enter it. Click Log in. The members of the Guardian Team approve the sign-in on their devices, in the mobile app. When the vote passes, click Login to return to the service provider, signed in.

Troubleshooting

Issue Solution
Google asks for a password instead of redirecting SSO is not enabled, or the profile is not assignedCheck Enable SSO with third-party identity provider and the profile assignment
Google rejects the SAML assertion The certificate in Google does not matchDownload the certificate again from the SAML endpoints card and upload it to Google
Google reports an issuer or entity ID mismatch Domain Name differs from the domain the user signs in toCreate the connected app again with your primary Google Workspace domain
Google reports that the account was not found The email in the access form is not a Google userEnter the user’s Google Workspace email exactly
A super administrator signs in with a password Super administrators bypass SSO by defaultUse a Services Administrator for the SplitSecure admin user
Starting from Google shows “This sign-in request asks for an ACS this app doesn’t list” The connected app was created before it listed the www.google.com (opens in a new tab) ACSCreate the connected app again, or start the sign-in from SplitSecure

External resources