Set up a VictorOps connector

Capabilities
Gather VictorOps credentials
Create an API key
Configure the VictorOps connector

Capabilities

Resource	Sync	Provision
Accounts
Teams
Schedules

Gather VictorOps credentials

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

A user with the admin role in VictorOps must perform this task.

Create an API key

In VictorOps, navigate to Integrations > API.

Carefully copy and save the API ID shown at the top of the page.

Click New Key.

Generate a new API key.Select Read-only to give C1 READ permission to your VictorOps instance.If you want to provision access to VictorOps teams using C1, this requires READ/WRITE access, so do not select this option.

Carefully copy and save the newly generated API key.

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

Configure the VictorOps connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in C1
Access to the set of VictorOps credentials generated by following the instructions above

Cloud-hosted
Self-hosted

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

In C1, navigate to Integrations > Connectors and click Add connector.

Search for VictorOps and click Add.

Choose how to set up the new VictorOps 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 C1)
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 C1 users. Setting multiple owners is allowed.If you choose someone else, C1 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 ID into the API ID field.

Paste the API key into the API key field.

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

The VictorOps 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 VictorOps connector

In C1, navigate to Integrations > Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new VictorOps 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 C1)
Add the connector to a managed app (select from the list of existing managed apps)
Create a new managed app

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

Secrets configuration

# baton-victorops-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-victorops-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # VictorOps credentials
  BATON_VICTOROPS_API_ID: <VictorOps API ID>
  BATON_VICTOROPS_API_KEY: <VictorOps API key>

  # 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-victorops.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-victorops
  labels:
    app: baton-victorops
spec:
  selector:
    matchLabels:
      app: baton-victorops
  template:
    metadata:
      labels:
        app: baton-victorops
        baton: true
        baton-app: victorops
    spec:
      containers:
      - name: baton-victorops
        image: ghcr.io/conductorone/baton-victorops:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-victorops
        envFrom:
        - secretRef:
            name: baton-victorops-secrets

Step 3: Deploy the connector

Create a namespace in which to run C1 connectors (if desired), then apply the secret config and deployment config files.

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 VictorOps connector to. VictorOps data should be found on the Entitlements and Accounts tabs.

That’s it! Your VictorOps connector is now pulling access data into C1.

Set up a Splunk connector

Set up a Sumo Logic connector

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a VictorOps connector

Capabilities

Gather VictorOps credentials

Create an API key

Configure the VictorOps connector

Resources

Step 1: Set up a new VictorOps connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

​Capabilities

​Gather VictorOps credentials

​Create an API key

​Configure the VictorOps connector

​Resources

​Step 1: Set up a new VictorOps connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather VictorOps credentials

Create an API key

Configure the VictorOps connector

Resources

Step 1: Set up a new VictorOps connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector