Capabilities

Available hosting methods

Choose the hosting method that best suits your needs:

Gather Google BigQuery credentials

Each setup method 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.

That’s it! Next, move on to the instructions for your chosen setup method.

Set up a Google BigQuery cloud-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Google BigQuery credentials generated by following the instructions above

1. In ConductorOne, click Connectors > Add connector.

2. Search for Google BigQuery and click Add.

3. Choose how to set up the new Google BigQuery 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 ConductorOne)

   • 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 ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne 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. Upload the JSON file you created in the Credentials (JSON) field.

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.

That’s it! Your Google BigQuery connector is now pulling access data into ConductorOne.

Set up a Google BigQuery cloud-hosted connector using Terraform

As an alternative to the cloud-hosted setup process described above, you can use Terraform to configure the integration between Google BigQuery and ConductorOne.

See the ConductorOne Google BigQuery integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.

Set up a Google BigQuery self-hosted connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in ConductorOne
• Access to the set of Google BigQuery credentials generated by following the instructions above

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

Why use Kubernetes? Kubernetes provides automated deployment, scaling, and management of your connectors. It ensures high availability and reliable operation of your connector services.

Step 1: Configure the Google BigQuery connector

1. In ConductorOne, navigate to Connectors > Add connector.

2. Search for Baton and click Add.

3. Choose how to set up the new Google BigQuery 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 ConductorOne)

   • 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 ConductorOne users. Setting multiple owners is allowed.

   If you choose someone else, ConductorOne 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 Google BigQuery connector deployment:

Secrets configuration

# baton-google-bigquery-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-google-bigquery-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne 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: ghcr.io/conductorone/baton-google-bigquery:latest
        args: ["service"]
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-google-bigquery-secrets

Step 3: Deploy the connector

1. Create a namespace in which to run ConductorOne connectors (if desired):

   kubectl create namespace baton-google-bigquery
   

2. Apply the secret configuration:

   kubectl -n baton-google-bigquery apply -f baton-google-bigquery-secrets.yaml
   

3. Apply the deployment:

   kubectl -n baton-google-bigquery apply -f baton-google-bigquery.yaml
   

Step 4: Verify the deployment

1. Check that the deployment is running:

   kubectl -n c1 get pods
   

2. View the connector logs:

   kubectl -n c1 logs -l app=baton-${baton-google-bigquery}
   

3. Check that the connector data uploaded correctly. In ConductorOne, click Applications. 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.

That’s it! Your Google BigQuery connector is now pulling access data into ConductorOne.