Search the documentation
Search the documentation...
SplitSecure documentation

On this page

Procedure · 8 steps

Google Workspace

Sign in to Google Workspace through SplitSecure, so each sign-in waits for your Guardian Team to approve it.

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, so the users you choose sign in to Google only when your Guardian Team, the group of devices that together approve each proposal, approves it. You add SplitSecure as a third-party SSO (single sign-on) profile in Google, assign the profile to an organizational unit or group, and create the matching connected app.

Values you exchange

Value Where to find it Where to paste it
SAML IdP Entity ID The identity provider’s SAML endpoints card in the Web App Google, IDP entity ID, in Enter the identity provider details
SSO URL (HTTP-Redirect) The same card Google, Sign-in page URL, in the same step
Signing certificate (PEM) The same card, Download Certificate → PEM format Google, Upload certificate, in the same step
Google SP Entity ID Google, SP details, in Copy the service provider details The Web App, Entity ID, in Create the connected app

Add SplitSecure as an 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. Enter a profile name, for example SplitSecure.
  4. For Autofill email, select Send email address in the URL as the LoginHint parameter.

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
IDP entity ID The SAML IdP Entity IDFrom the SAML endpoints card
Sign-in page URL The SSO URL (HTTP-Redirect)From the SAML endpoints card, not the SSO URL (HTTP-Post)
Upload certificate The certificate fileDownload Certificate → PEM format on the card

Click Save.

After the save, Google shows the SP details section. Copy the Entity ID. It looks like https://accounts.google.com/samlrp/.... You paste it into the Web App in Create the connected app below.

  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 SplitSecure profile.
  6. Choose Have Google prompt for their username, then redirect them to this profile’s IDP sign-in page.
  7. Click Save.

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 (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 Entity ID, paste the Google SP Entity ID from Copy the service provider details. The Web App derives the rest of the Google endpoints from it.

  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 Email of a Google user in the organizational unit or group you assigned.

  1. In the test profile, open a Google service, for example https://mail.google.com.
  2. Enter the email of a user in the assigned organizational unit or group.
  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 The SSO profile is not assigned to the userAssign the profile to the user’s organizational unit or group
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 rejects the issuer IDP entity ID does not matchCompare it with the SAML IdP Entity ID on the SAML endpoints card
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
SSO works for some users but not others Only part of the organization has the profile assignedCheck every organizational unit and group that must use the profile
A super administrator signs in with a password SSO profiles do not apply to super administratorsUse the Google Workspace (Legacy) guide

External resources