Set up a Google Looker connector

C1 provides identity governance for Looker. Integrate your Looker instance with C1 for unified visibility and governance over user access.

This connector is in beta. This means it’s undergoing ongoing testing and development while we gather feedback, validate functionality, and improve stability. Beta connectors are generally stable, but they may have limited feature support, incomplete error handling, or occasional issues.

We recommend closely monitoring workflows that use this connector and contacting our Support team with any issues or feedback.

Capabilities

Resource	Sync	Provision
Account
Group
Role

Additional functionality:

• User lifecycle actions: enable_user and disable_user, which reactivate or deactivate a Looker user by toggling is_disabled.

Account creation follows Looker’s official provisioning flow: the connector creates the user record, sets the login email via an email credential, and sends the user a password-setup email. No password is ever generated or transmitted by the connector — the user sets one through the emailed link, or signs in through SSO (SAML, OIDC, LDAP) where the identity provider owns the login.

Gather Looker configuration information

Configuring the connector requires you to pass in information from Looker. Gather these configuration details before you move on.

Here’s the information you’ll need:

• Base URL (e.g. https://your.looker.com:19999)
• Client ID
• Client Secret

The Client ID and Client Secret come from an API3 key, generated in the Looker Admin UI (Admin > Users > Edit Keys). The key inherits the permissions of the user it belongs to: syncing requires the see_users, see_groups, and see_roles permissions; provisioning (account create/delete and lifecycle actions) requires the Admin role.

See the Looker docs for information on how to acquire credentials: View the documentation

Configure the Looker connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Looker configuration information gathered by following the instructions above

Cloud-hosted

Follow these instructions to use a built-in, no-code connector hosted by C1.

1. In C1, navigate to Integrations > Connectors and click Add connector.

2. Search for Looker and click Add.

3. Choose how to set up the new Looker connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. Find the Settings area of the page and click Edit.

7. Enter the configuration information from the previous section.

8. Click Save.

9. The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.

Done. Your Looker connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Looker connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with C1, automatically syncing and uploading data at regular intervals. This data is immediately available in the C1 UI for access reviews and access requests.

Resources

Contact C1’s support team to download the latest version of the connector.

Step 1: Set up a new Looker connector

1. In C1, navigate to Integrations > Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Looker connector:

   • Add the connector to a currently unmanaged app (select from the list of apps that were discovered in your identity, SSO, or federation provider that aren’t yet managed with C1)

   • Add the connector to a managed app (select from the list of existing managed apps)

   • Create a new managed app

4. Set the owner for this connector. You can manage the connector yourself, or choose someone else from the list of C1 users. Setting multiple owners is allowed.

   If you choose someone else, C1 will notify the new connector owner by email that their help is needed to complete the setup process.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. Click Rotate to generate a new Client ID and Secret.

   Carefully copy and save these credentials. We’ll use them in Step 2.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Looker connector deployment:

Secrets configuration

# baton-looker-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-looker-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>

  # Looker config
  BATON_LOOKER_BASE_URL: <The base URL for the Looker API, e.g. https://your.looker.com:19999>
  BATON_LOOKER_CLIENT_ID: <The Client ID for the Looker API>
  BATON_LOOKER_CLIENT_SECRET: <The Client Secret for the Looker API>

  # Enable provisioning (account create/delete and lifecycle actions)
  BATON_PROVISIONING: "true"

See the connector’s README or run --help to see all available configuration flags and environment variables.

Deployment configuration

# baton-looker.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-looker
  labels:
    app: baton-looker
spec:
  selector:
    matchLabels:
      app: baton-looker
  template:
    metadata:
      labels:
        app: baton-looker
        baton: true
        baton-app: looker
    spec:
      containers:
      - name: baton-looker
        image: public.ecr.aws/conductorone/baton-looker:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-looker
        envFrom:
        - secretRef:
            name: baton-looker-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

2. Check that the connector data uploaded correctly. In C1, click Apps. On the Managed apps tab, locate and click the name of the application you added the Looker connector to. Looker data should be found on the Entitlements and Accounts tabs.

Done. Your Looker connector is now pulling access data into C1.