Set up a Rootly connector

Capabilities

Resource	Sync	Provision
Accounts
Teams
Schedules
Secrets

This connector can sync secrets and display them on the Inventory page.

Gather Rootly credentials

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

A user with permission to create API keys in Rootly must perform this task.

Create new Rootly roles

In Rootly, navigate to Configuration > Roles and permissions > Configuration.

Click Create role.

On the Incident Response tab, click Custom Roles > Create Role.

Set the Teams:Read and Secrets:Read permissions, then click Create.

On the On-Call tab, click Custom Roles > Create Role.

Set the Teams Permissions:Read and Schedules Permissions:Read permissions, then click Create.

Create a Rootly API key

In Rootly, navigate to Configuration > API Keys.

Click Generate New API Key.

When prompted to select an API key type, select Global API Key.

Give the new API key the incident response and on-call roles you created above.

Give the new key a name, such as “ConductorOne”, and a description, then set an expiration.

Click Create.

Carefully copy and save the new API key.

Note that if you ever edit a Rootly role used on an API key, the existing key will not receive changes to the role permissions. You must generate a new API key. That’s it! Next, move on to the connector configuration instructions.

Configure the Rootly connector

To complete this task, you’ll need:

The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Rootly 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 Rootly and click Add.

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

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

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

In ConductorOne, navigate to Connectors > Add connector.

Search for Baton and click Add.

Choose how to set up the new Rootly 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 Rootly connector deployment:

Secrets configuration

# baton-rootly-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-rootly-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Rootly credentials
  BATON_API_KEY: <Rootly API key>

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

Deployment configuration

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

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

Welcome

Build connectors

Configure connectors

Deploy connectors

Upload connector data

Connector library

Capabilities

Gather Rootly credentials

Create new Rootly roles

Create a Rootly API key

Configure the Rootly connector

Step 1: Set up a new Rootly 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 Rootly credentials

​Create new Rootly roles

​Create a Rootly API key

​Configure the Rootly connector

​Step 1: Set up a new Rootly connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Rootly credentials

Create new Rootly roles

Create a Rootly API key

Configure the Rootly connector

Step 1: Set up a new Rootly connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector