Set up an Incident.io connector

Capabilities

Resource	Sync	Provision
Accounts
Schedules
Base roles
Custom roles

Gather Incident.io credentials

Each setup method requires you to pass in credentials generated in Incident.io. Gather these credentials before you move on.

Generate an API token

In Incident.io, navigate to your account and click API Keys.

Generate a new API key, giving it the View data and Read schedules permissions.

Carefully copy and save the API key.

Done. Next, move on to the connector configuration instructions.

Configure the Incident.io connector

To complete this task, you’ll need:

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

Search for Incident.io and click Add.

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.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

Find the Settings area of the page and click Edit.

Paste the API token into the Incident.io API token field.

Click Save.

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

Done. Your Incident.io connector is now pulling access data into C1.

Follow these instructions to use the Incident.io 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: Configure the Incident.io connector

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

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

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 Incident.io connector deployment:

Secrets configuration

# baton-incident-io-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-incident-io-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Incident.io credentials
  BATON_TOKEN: <Incident.io API token>

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

Deployment configuration

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

Done. Your Incident.io connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up an Incident.io connector

Capabilities

Gather Incident.io credentials

Generate an API token

Configure the Incident.io connector

Resources

Step 1: Configure the Incident.io connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather Incident.io credentials

​Generate an API token

​Configure the Incident.io connector

​Resources

​Step 1: Configure the Incident.io connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Incident.io credentials

Generate an API token

Configure the Incident.io connector

Resources

Step 1: Configure the Incident.io connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector