Set up Metabase connector

C1 provides identity governance and just-in-time provisioning for Metabase. Integrate your Metabase instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

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.

Support

This connector is compatible with Metabase versions 0.49 and newer. Older versions are not supported.

Due to the nature of Metabase’s API versioning model, three versions of this connector are currently available for installation:

• Metabase (unversioned)
• Metabase v0.49
• Metabase v0.56

See the docs below for details on the capabilities of each version and instructions on installing your preferred version.

Capabilities

Metabase (unversioned)

Resource	Sync	Provision
Account
Group

The Metabase connector supports automatic account provisioning.

When a new account is created by C1, the account’s password will be sent to a vault.

The Metabase connector cannot fully deprovision accounts, but it can enable and disable existing accounts.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

Action name	Additional fields	Description
enable_user	user_id (string, required)	Activates a deactivated Metabase user account
disable_user	user_id (string, required)	Deactivates a Metabase user account

Metabase v0.49

Resource	Sync	Provision
Account
Database
Group

The Metabase v0.49 connector supports automatic account provisioning.

When a new account is created by C1, the account’s password will be sent to a vault.

The Metabase v0.49 connector cannot fully deprovision accounts, but it can enable and disable existing accounts.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

Action name	Additional fields	Description
enable_user	user_id (string, required)	Activates a deactivated Metabase user account
disable_user	user_id (string, required)	Deactivates a Metabase user account

Metabase v0.56

Resource	Sync	Provision
Account
Database
Group

The Metabase v0.56 connector supports automatic account provisioning.

When a new account is created by C1, the account’s password will be sent to a vault.

The Metabase v0.56 connector cannot fully deprovision accounts, but it can enable and disable existing accounts.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

Action name	Additional fields	Description
enable_user	user_id (string, required)	Activates a deactivated Metabase user account
disable_user	user_id (string, required)	Deactivates a Metabase user account

Gather Metabase configuration information

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

Here’s the information you’ll need:

• API Key
• Base URL

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

This connector requires the following scopes:

• Query builder and native

Learn how to set the scopes

Configure the Metabase connector

To complete this task, you’ll need:

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

2. As relevant, search for Metabase, Metabase v0.49 or Metabase v0.56 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. Enter the configuration information from the previous section.

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 Metabase connector is now pulling access data into C1.

Self-hosted

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

Use the relevant files below to create two Kubernetes manifest files for your Metabase connector deployment.

Metabase (unversioned)

Secrets configuration

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

  # Metabase config
  BATON_METABASE_API_KEY: <Metabase API Key>
  BATON_METABASE_BASE_URL: <Metabase Base URL>

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

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

Deployment configuration

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

Metabase v0.49

Secrets configuration

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

  # Metabase config
  BATON_METABASE_API_KEY: <Metabase API Key>
  BATON_METABASE_BASE_URL: <Metabase Base URL>

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

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

Deployment configuration

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

Metabase v0.56

Secrets configuration

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

  # Metabase config
  BATON_METABASE_API_KEY: <Metabase API Key>
  BATON_METABASE_BASE_URL: <Metabase Base URL>

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

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

Deployment configuration

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

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