Set up a Google BigQuery connector

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

Capabilities

Resource	Sync	Provision
Accounts
Service accounts
Roles
Datasets

Gather Google BigQuery credentials

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

A user with the permission to make a service account in Google Cloud must perform this task.

Create a service account

1. In the Google Cloud console, navigate to the Create service account page.

2. Select your project.

3. Choose a name for the service account and enter it in the Service account name field.

   Google Cloud automatically sets the service account ID based on the name you choose.

4. Enter a description for the service account in the Service account description field.

5. Click Create and continue.

6. From the Select a role list, grant the service account either the Viewer or BigQuery Data Viewer role.

7. Click Continue.

8. Click Done to create the service account.

Create a service account key

1. Still in the Google Cloud console, click the email address of the service account you created in Step 1.

2. Click Keys.

3. Click Add key > Create new key.

4. Click Create. A JSON file containing the account key is created and downloaded. Keep the downloaded file safe, you’ll use it to set up the connector.

5. Click Close.

Done. Next, move on to the connector configuration instructions.

Configure the Google BigQuery connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Google BigQuery credentials generated 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 Apps > Connectors and click Add connector.

2. Search for Google BigQuery and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

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

8. Upload the JSON file you created in the Credentials (JSON) field.

9. Click Save.

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

Done. Your Google BigQuery connector is now pulling access data into C1.

Self-hosted

Follow these instructions to use the Google BigQuery 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

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Google BigQuery connector

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

2. Search for Baton and click Add.

3. Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).

   If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

4. Set the connector’s Name and, optionally, a Description.

5. Click the pencil icon next to Owners to choose who can configure and manage this connector.

6. Click Add. The connector is created and its configuration page opens.

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

8. 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 Google BigQuery connector deployment:

Secrets configuration

# baton-google-bigquery-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-google-bigquery-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
data:
  # Google BigQuery credentials
  BATON_CREDENTIALS_JSON: <base64 encoded credentials JSON>

Base64 Encoding: Use echo -n "your-value" | base64 to encode your secrets.

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

Deployment configuration

# baton-google-bigquery.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-google-bigquery
  labels:
    app: baton-google-bigquery
spec:
  selector:
    matchLabels:
      app: baton-google-bigquery
  template:
    metadata:
      labels:
        app: baton-google-bigquery
        baton: true
        baton-app: google-bigquery
    spec:
      containers:
      - name: baton-google-bigquery
        image: public.ecr.aws/conductorone/baton-google-bigquery:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-google-bigquery
        envFrom:
        - secretRef:
            name: baton-google-bigquery-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 Google BigQuery connector to. Google BigQuery data should be found on the Entitlements and Accounts tabs.

Done. Your Google BigQuery connector is now pulling access data into C1.