Skip to main content

Set up single sign-on (SSO) with Google Workspace

J
Written by JP Arredondo

Known limitations

Everyone in the organization can sign in. Google can't limit an OAuth client to some users or groups, so use another identity provider if only part of the organization should get in. The redirect URI is specific to your Sana workspace, so you need one registration per Sana workspace.


Before setup

Ask your Sana contact for the redirect URI of your Sana workspace.


Setup

Sign in with Google for one Google Workspace organization: create an OAuth client in the Google Cloud console, then send its client ID and client secret to your Sana contact.

Everything below happens in the Google Cloud console. The Admin console's SSO with third party IdP → Add OIDC profile sounds similar but does the reverse: it makes Gmail and other Google services sign users in through another identity provider, such as Okta. It does not apply here.

1. Open a project inside your organization

Sign in to console.cloud.google.com with a Google Workspace account that can edit the project (for example Owner or Editor), and pick or create a project, for example sana-sso.

Its Organization must be your organization (for example acme.com): the Internal audience in step 2 exists only for projects inside an organization. No API needs enabling.

2. Configure Google Auth Platform with audience Internal

Google Auth Platform → Get started, or its Audience page if the project already has one.

Field on this screen

What to put

App name

Shown on Google's account chooser, for example Sana.

User support email

An address your team monitors.

Audience

Internal. If it's greyed out, the project is not in an organization: go back to step 1.

Contact information

Where Google sends notices about the project.

Accept the policy and click Create. Nothing to add under Data Access, and an internal app needs no verification.

Important: Never use an External audience. Every Google account shares one issuer and Sana does not check the account's domain, so with External anyone with a Gmail address who knows the workspace URL becomes a member of your Sana workspace.

3. Create the OAuth client

Google Auth Platform → Clients → Create client:

Field on this screen

What to put

Application type

Web application, the only type with a client secret and redirect URIs.

Name

Internal only, for example Sana.

Authorized JavaScript origins

Leave empty.

Authorized redirect URIs

The redirect URI from your Sana contact, exactly as you received it, with no trailing slash. It looks like this:

  • EU workspaces: https://sana-eu.myworkday.com/x-api/<workspace ID>/auth/oidc/callback

  • US workspaces: https://sana.myworkday.com/x-api/<workspace ID>/auth/oidc/callback

4. Copy the credentials (the secret is shown once)

The dialog after Create shows the Client ID and Client secret. Copy both, or click Download JSON, before closing it: afterwards Google only shows the secret's last four characters.

  • Lost the secret? Click Add secret on the client rather than creating a new client.

  • To rotate: click Add secret (two at most), send the new secret to your Sana contact, then disable and delete the old one in Google once Sana confirms the switch.

5. Send the credentials to Sana

Send the Client ID and Client secret to your Sana contact. Your Sana contact will tell you how to share the client secret securely; don't send it in a regular email or chat message.

Did this answer your question?