ConductorOne docs

Set up a Verkada connector

ConductorOne provides identity governance and just-in-time provisioning for Verkada. Integrate your Verkada instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision access.

Capabilities

Resource	Sync	Provision
Accounts	✅
Access groups	✅	✅
Access users	✅

Gather Verkada credentials

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

A user with Org Admin permissions in Verkada must perform this task.

Generate a Verkada API key

In Verkada click Admin Home.
Click Verkada API and select + New API Key.
Give the new API key a name, such as “ConductorOne integration”.
Select the relevant permission:
- Read/write if you want to use ConductorOne to provision Verkada group membership
- Read only if you do not want to use ConductorOne to provision Verkada group membership
Select an expiration for the API key, then click Generate API key.
Carefully and copy and save the new API key.

That’s it! Next, move on to the connector configuration instructions.

Configure the Verkada connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Verkada credentials generated 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.
Search for Verkada and click Add.
Choose how to set up the new Verkada 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.
Paste the API key into the API key field.
Select your Verkada region (United States or European Union).
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 Verkada connector is now pulling access data into ConductorOne.

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

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Verkada 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

Create two Kubernetes manifest files for your Verkada connector deployment:

Secrets configuration

# baton-verkada-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-verkada-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Verkada credentials
  BATON_API_KEY: <Verkada API key>
  BATON_REGION: <US (default) or EU>

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

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