nano SIEM
SettingsSingle Sign-On

Google Workspace

Supported in:Self-hosted

Connect Google Workspace to nano with OIDC using a Google Cloud OAuth 2.0 client.

Connect Google Workspace to let your team sign in to nano with OIDC. Create an OAuth 2.0 web client in Google Cloud, then add its credentials in nano.

For how SSO works in nano, see Single Sign-On.

Prerequisites

  • A Google Cloud project in the same organization as your Workspace. You need permission to configure the project's Google Auth Platform and create OAuth clients (for example the Owner or OAuth Config Editor role).
  • A nano user with full administrator authority. Creating or enabling a provider, and setting the delegated administrator or service-account key, need it, not only settings:system. See Who can change providers.
  • Your nano origin (see below). Also a provider slug (this guide uses google).
  • Existing IdP groups to map to nano grants, or existing invited members for invitation-only access.

App registration

DeploymentAuthorized JavaScript originAuthorized redirect URI
Self-runhttps://<your-nano-host>https://<your-nano-host>/auth/callback/google (the provider form shows the exact value for your slug)

Select or create a Google Cloud project in your Workspace organization at console.cloud.google.com.

Set the audience to Internal. In the Cloud Console open Google Auth Platform. Under Branding, fill in the app name and support email. Under Audience, set User type to Internal, which restricts sign-in to accounts in your Workspace organization. (Older consoles show this as APIs & Services → OAuth consent screen → User Type: Internal.)

Create the OAuth client. In Google Auth Platform → Clients, choose Create client and set Application type to Web application. Name it, for example nano. Under Authorized JavaScript origins, add the origin above. Under Authorized redirect URIs, add the redirect URI above. Click Create.

Copy the credentials. Google shows the Client ID and Client secret. Keep them for the next step.

Emit/lookup groups

Google's ID token has no groups claim. nano checks only the groups you map using the Admin SDK Directory API members.hasMember, with the read-only admin.directory.group.member.readonly scope. It never requests group-write or user-management scopes. Direct and nested membership work within the same Workspace domain; unsupported cross-domain nesting fails closed. See Google's membership API.

  1. In the Google Cloud project, enable Admin SDK API.
  2. Create a dedicated service account, enable Google Workspace domain-wide delegation, and note its numeric OAuth client ID. Download one JSON key and keep it private.
  3. A Workspace super administrator opens Security → Access and data control → API controls → Manage Domain Wide Delegation. Add that service account's client ID with exactly https://www.googleapis.com/auth/admin.directory.group.member.readonly. This administrative authorization is separate from the OAuth sign-in client.
  4. Choose a delegated Workspace administrator with permission to read group memberships. Enter its primary email in nano's Delegated administrator field. Use the narrowest administrator privileges your Workspace supports.
  5. Paste the JSON key into Service account key in the provider form. nano encrypts it at rest like the OIDC client secret and never returns the key. Leave it empty on later edits to keep it; use Remove the stored key to remove it. Rotate the key in Google and replace it in nano when needed.

Without both the service account and delegated administrator, the form shows Invitation-only and no new members are provisioned. If configured credentials fail (API disabled, denied delegation, expired key, unsupported nested group), nano refuses sign-in; it never treats unknown membership as allowed.

nano provider form

In Settings → Single Sign-On → Add provider, enter:

FieldValue
NameGoogle Workspace
Sluggoogle
Issuer URLhttps://accounts.google.com
Client ID(from Google)
Client secret(from Google)
Scopesopenid email profile

Save, and make sure Provider enabled is on.

Group mappings

Map each group's email address (for example analysts@example.com) or immutable Directory group ID. Google has no ID-token groups claim; leave the claim field unused.

Map to nano groups. Leave Create accounts for users in mapped groups on (the default). A new member receives exactly these grants; no default Everyone or ReadOnly grant is added. Turning it off, or leaving mappings empty, keeps access invitation-only.

Existing invited, active members can link using the same verified email and retain their manual grants. Membership and provider-owned grants re-sync on every sign-in; manual grants and grants owned by other providers survive. Client secrets and service account keys are encrypted when saved and never returned by the provider API; blank secret fields on edit keep stored values.

Test

Use a private window and keep an administrator session open:

  1. Allowed new user: sign in with an account in a mapped IdP group. Confirm creation and exactly the mapped groups, without a default grant.
  2. Outsider: try a new account outside all mapped groups. Confirm sign-in is denied and no member is created.
  3. Invited member: sign in with an existing invited, active member whose email is verified by the IdP. Confirm linking and preserved manual access.
  4. Removal: remove the allowed user from the IdP group, then sign in again. Confirm provider-owned grants are removed; manual grants remain. A JIT member without any mapped group is denied.
  5. Lookup failure: in a disposable test configuration, remove the service account's domain-wide delegation. Confirm sign-in is refused with the membership-verification error.

These steps apply to nano Self-run. SSO settings are hidden when the installation does not provide the SSO capability (the open-source edition).

Security notes

  • Restrict to your organization. An Internal audience means only accounts in your Workspace can complete the Google sign-in. Without it, any Google account could reach nano's token check.
  • First-time SSO members need a mapped IdP group and receive only its mapped grants. Existing invited, active members retain their manually assigned access.
  • New SSO users receive no default Everyone or ReadOnly grant. SSO grants re-sync at sign-in; manual grants survive removal from an IdP group.
  • Google ID tokens carry email_verified: true for Workspace accounts. nano requires a verified email to create or link an account. Verified domains doesn't apply to Google.

Troubleshooting

Need help with these checks? Contact support with the request ID and time with timezone.

Every refused sign-in has a reason in the platform audit log. See Denied sign-ins.

  • Group membership could not be verified (membership_unknown). Sign-in is denied when the Directory lookup fails, including for invited members. Check the Admin SDK API, domain-wide delegation, the key and the delegated administrator. No partial lookup grants access.
  • Account is not in an allowed group (group_not_allowed). Check the exact mapped group email or ID and the user's current membership. A new member needs at least one mapping.
  • redirect_uri_mismatch. The Authorized redirect URI in the Google OAuth client must exactly match the value in App registration.
  • Issuer mismatch. Use exactly https://accounts.google.com, with no trailing slash.
  • "Access blocked" or user outside your organization. The consent screen must be Internal, and the user must belong to your Workspace organization.
  • A user can't sign in. Confirm a mapped group and working delegated lookup, or an existing invited, active membership with the same verified email.

What's next

On this page