This is an updated and improved version of the Google Workspace integration! If you’re setting up a Google Workspace integration with ConductorOne for the first time, you’re in the right place.

Capabilities

Gather Google Workspace credentials

Configuring the connector requires you to pass in credentials generated in Google Workspace. Gather these credentials before you move on.

A user with the Super Admin role in Google Workspace must perform this task.

Create a new project

1. As a Google Workspace Super Admin, sign in to https://console.cloud.google.com.

2. In the toolbar, click the project select dropdown, and click NEW PROJECT.

   

   

3. Create a new project for your organization:

   • Project Name: Choose a names, such as “ConductorOne Integration”
   • Organization/Location: Choose the appropriate Organization/Location

   

4. After the project is created, make sure the correct project is selected in the dropdown at the top.

   

Enable the API

1. In the navigation menu, navigate to > APIs & Services > Library.

   

2. Search for and select the Admin SDK API.

   

3. Click Enable.

   

Create a service account

1. In the navigation menu, navigate to > APIs & Services > Credentials.

   

2. Select CREATE CREDENTIALS > Service Account.

   

3. Under Service account details, fill in the following:

   • Service account name: ConductorOne Integration
   • Service account description: for example, “Service account for ConductorOne Google Workspace Integration”
   • Click CREATE AND CONTINUE

   

4. Under Grant this service account access to a project, grant the Editor role.

   

5. Leave Grant users access to this service account blank.

6. Click DONE.

   

Get credentials

1. Navigate back to APIs & Services > Credentials and select the service account you just created.

2. Click the service account’s email address. Locate and save the Unique ID.

3. On the Service Account Details Page, click KEYS.

4. Click ADD KEY > Create new key.

5. Choose JSON and click CREATE.

6. Keep the downloaded file somewhere safe.

Add the service account to Google Workspace

1. Go to https://admin.google.com as a SUPER ADMIN.

2. In the navigation menu, select Security > Access and data control > API Controls.

3. Click MANAGE DOMAIN WIDE DELEGATION.

4. Click Add new and fill out the form:

   • Client ID: The service account’s unique ID

   • OAuth Scopes: Copy and paste in the relevant scopes

     • Use the following scopes to give ConductorOne READ access (for syncing access data):

       https://www.googleapis.com/auth/admin.directory.user.alias.readonly,https://www.googleapis.com/auth/admin.directory.rolemanagement.readonly,https://www.googleapis.com/auth/admin.directory.group.member.readonly,https://www.googleapis.com/auth/admin.directory.group.readonly,https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/admin.directory.domain.readonly,https://www.googleapis.com/auth/admin.reports.audit.readonly
       

     • Use the following scopes to give ConductorOne READ/WRITE access (for syncing access data and provisioning access):

       https://www.googleapis.com/auth/admin.directory.user.alias.readonly,https://www.googleapis.com/auth/admin.directory.rolemanagement,https://www.googleapis.com/auth/admin.directory.group.member,https://www.googleapis.com/auth/admin.directory.group,https://www.googleapis.com/auth/admin.directory.user.readonly,https://www.googleapis.com/auth/admin.directory.domain.readonly,https://www.googleapis.com/auth/admin.reports.audit.readonly
       

5. Click AUTHORIZE.

   

6. In the navigation menu, select Account > Account Settings.

7. Copy the Customer ID from this page.

Locate your primary domain

1. In the navigation panel on the left, click Account > Domains.

2. Click Manage Domains. Locate and copy the domain labeled as the Primary Domain in the Type column.

That’s it! Next, move on to the connector configuration instructions.

Configure the Google Workspace connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

# baton-google-workspace-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-google-workspace-secrets
type: Opaque
data:
  # ConductorOne credentials
  BATON_CLIENT_ID: <base64 encoded ConductorOne client ID>
  BATON_CLIENT_SECRET: <base64 encoded ConductorOne client secret>
  
  # Google Workspace specific credentials
  BATON_CUSTOMER_ID: <base64 encoded customer ID>
  BATON_DOMAIN: <base64 encoded domain>
  BATON_ADMINISTRATOR_EMAIL: <base64 encoded administrator email>
  BATON_CREDENTIALS_JSON: <base64 encoded credentials JSON>

  # Optional: include if you want ConductorOne to provision access using this connector
  BATON_PROVISIONING: true

# baton-google-workspace.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-google-workspace
  labels:
    app: baton-google-workspace
spec:
  selector:
    matchLabels:
      app: baton-google-workspace
  template:
    metadata:
      labels:
        app: baton-google-workspace
        baton: true
        baton-app: google-workspace
    spec:
      containers:
      - name: baton-google-workspace
        image: ghcr.io/conductorone/baton-google-workspace:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-google-workspace-secrets

What’s next?

If Google Workspace is your company’s identity provider (meaning that it is used to SSO into other software), the integration sync will automatically create applications in ConductorOne for all of your SCIMed software. Before you move on, review the Create applications page for important information about how to set up integrations with the SCIMed apps.