Set up Metabase connector

ConductorOne provides identity governance and just-in-time provisioning for Metabase. Integrate your Metabase instance with ConductorOne 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 ConductorOne, 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.

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 ConductorOne, 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.

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 ConductorOne, 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.

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 ConductorOne
Access to the set of Metabase configuration information gathered by following the instructions above

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

In ConductorOne, navigate to Admin > Connectors and click Add connector.
As relevant, search for Metabase, Metabase v0.49 or Metabase v0.56 and click Add.
Choose how to set up the new Metabase 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
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.
Click Next.
Find the Settings area of the page and click Edit.
Enter the configuration information from the previous section.
Click Save.
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 Metabase connector is now pulling access data into ConductorOne.

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 ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Set up a new Metabase connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Metabase 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
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.
Click Next.
In the Settings area of the page, click Edit.
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:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>

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

  # Optional: include if you want ConductorOne 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: ghcr.io/conductorone/baton-metabase:latest
        imagePullPolicy: IfNotPresent
        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:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>

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

  # Optional: include if you want ConductorOne 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: ghcr.io/conductorone/baton-metabase-v049:latest
        imagePullPolicy: IfNotPresent
        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:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>

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

  # Optional: include if you want ConductorOne 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: ghcr.io/conductorone/baton-metabase-v056:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-metabase-v056-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
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 metabase connector to. metabase data should be found on the Entitlements and Accounts tabs.

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