Set up a Rootly connector

C1 provides identity governance for Rootly. Integrate your Rootly instance with C1 for unified visibility and governance over user access.

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

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

2. Click Create role.

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

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

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

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

Create a Rootly API key

1. In Rootly, navigate to Configuration > API Keys.

2. Click Generate New API Key.

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

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

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

6. Click Create.

7. 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. Done. 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 C1
• Access to the set of Rootly 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 Rootly 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. Click Save.

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

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

Self-hosted

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

Secrets configuration

# baton-rootly-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-rootly-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 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: public.ecr.aws/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

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

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