Set up a Verkada connector

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

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

1. In Verkada click Admin Home.

2. Click Verkada API and select + New API Key.

3. Give the new API key a name, such as “C1 integration”.

4. Select the relevant permission:

   • Read/write if you want to use C1 to provision Verkada group membership

   • Read only if you do not want to use C1 to provision Verkada group membership

5. Select an expiration for the API key, then click Generate API key.

6. Carefully and copy and save the new API key.

Done. 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 C1
• Access to the set of Verkada 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 Verkada 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. Paste the API key into the API key field.

9. Select your Verkada region (United States or European Union).

10. Click Save.

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

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

Self-hosted

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 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 Verkada 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 Verkada connector deployment:

Secrets configuration

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

  # 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-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: public.ecr.aws/conductorone/baton-verkada:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-verkada
        envFrom:
        - secretRef:
            name: baton-verkada-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 Verkada connector to. Verkada data should be found on the Entitlements and Accounts tabs.

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