Set up an Incident.io connector

Capabilities
Gather Incident.io credentials
Generate an API token
Configure the 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.

That’s it! 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 ConductorOne
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 ConductorOne.

In ConductorOne, navigate to Admin > Connectors and click Add connector.

Search for Incident.io and click Add.

Choose how to set up the new Incident.io 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 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.

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

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

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Incident.io 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

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

Secrets configuration

# baton-incident-io-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-incident-io-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne 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: ghcr.io/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 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 Incident.io connector to. Incident.io data should be found on the Entitlements and Accounts tabs.

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

Set up IBM Blueworks Live connector

Set up an Ironclad connector

⌘I

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Set up an Incident.io connector

Capabilities

Gather Incident.io credentials

Generate an API token

Configure the Incident.io connector

Step 1: Configure the Incident.io connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

​Capabilities

​Gather Incident.io credentials

​Generate an API token

​Configure the Incident.io connector

​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

Step 1: Configure the Incident.io connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector