Single sign-on with Google Workspace
Gate treats your enterprise identity provider as core platform, not a bolt-on. Connecting Google Workspace means your team signs in to Kilimanjaro with their corporate Google identity — and only your domain's accounts get in, enforced at the platform's front door. Federation is native to the Identity-Aware Kernel; there's nothing to install.
You configure this once at the org level, under Org scope → Identity provider. Changing which identity providers your org trusts routes through Maker-Checker approval by default.
1. Prerequisites
In the Google Cloud console, create an OAuth 2.0 client for Kilimanjaro (or, for SAML, a Workspace SAML app):
- Note the client ID and client secret.
- Know the hosted domain(s) your workforce signs in from (e.g.
your-company.com).
You'll need an org-admin role in Kilimanjaro to add the provider.
2. Create the identity-provider config
In Org scope → Identity provider, add a provider and choose Google Workspace. Pick the protocol:
- OIDC via the native Google provider (recommended) — supply the issuer (
https://accounts.google.com), client ID, and client secret. Gate uses Google's standard authorize and token endpoints. - SAML — supply the Workspace SSO URL and signing certificate; the audience is Gate's entity ID.
The client secret is stored in the Vault on entry and referenced thereafter — never displayed again.
3. The hosted-domain allowlist is mandatory
This is the one thing you cannot skip. Gate enforces a hosted-domain (hd) allowlist: you list the Google Workspace domains permitted to sign in, and Gate rejects any token whose hd claim is not on the list — even if Google issued it. This is treated as a jurisdictional-ingress policy, and it is not disableable.
Why it matters: a plain "sign in with Google" accepts any Google account on the internet. The hd allowlist is what turns that into your company's SSO — a personal @gmail.com account, or an account from a different Workspace domain, is refused at the door regardless of valid Google credentials. Set this to your corporate domain(s) and nothing else gets in.
4. Map attributes and groups to roles
| Google claim | Maps to |
|---|---|
email | |
given_name | first name |
family_name | last name |
hd | hosted domain (allowlist check) |
Map Google Workspace groups to Kilimanjaro roles so a group like [email protected] grants the role you intend. Group membership is read at sign-in and drives role assignment.
5. Directory and group sync
Group membership and account state are resolved at each sign-in: when a user signs in, Gate reads their current group membership and applies the mapped roles, and just-in-time provisioning creates the account on first sign-in. A user removed from a Google group, or whose Workspace account is suspended, loses the corresponding access on their next sign-in attempt.
Google Workspace differs from Okta and Entra here: its directory is pull-based (queried via Google's Directory API) rather than push-based (SCIM), so there's no real-time deactivation push — reconciliation happens at the sign-in boundary. For most workforce SSO this is exactly what you want; if you need continuous out-of-band directory reconciliation, talk to your account team about the right pattern for your setup.
6. Availability
OIDC sign-in via the native Google provider and SAML federation are both available on every plan.
7. Test and verify
Sign in through the config's start URL (or your org's normal entry point, where Google now appears as an option). Confirm that an account on your allowlisted domain signs in and lands with the right role, that just-in-time provisioning created the account, and — importantly — that an account outside your hosted domain is refused. Check the audit log for both outcomes.
See also
- Okta SSO · Microsoft Entra ID SSO — the other workforce providers.
- Org scope — where org-level identity providers are configured.
- API → Auth — the federation substrate (OIDC / SAML / JIT).