Set up a Sentry connector

This is an updated and improved version of the Sentry connector! If you’re setting up Sentry with C1 for the first time, you’re in the right place.

Capabilities

Resource	Sync	Provision
Accounts
Projects
Teams
Organizations

The Sentry connector supports automatic account provisioning and deprovisioning.

Gather Sentry credentials

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

A user with an Admin role in Sentry must perform this task.

Create a Sentry API token

In Sentry, navigate to the settings menu and click Personal Tokens.

Click Create New Token.

On the Create New Personal Token page, give your the token a name, such as “C1”.

In the PERMISSIONS section of the page, give the token the relevant set of permissions:To sync (read) data:

Project: Read
Team: Read
Release: No Access
Issue & Event: Read
Organization: Read
Member: Read
Alerts: No Access

To sync and provision (read-write) data:

Project: Read & Write
Team: Read & Write
Release: No Access
Issue & Event: Read & Write
Organization: Read & Write
Member: Read & Write
Alerts: No Access

Scroll to the bottom of the page and click Save Changes.

Your new token is created. In the AUTH TOKENS section of the page, carefully copy and save the token value.

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

Optional: filter synced organizations

By default, the Sentry connector syncs all organizations accessible to the API token. If your Sentry account belongs to multiple organizations and you only want to sync a subset, you can provide a list of organization IDs or slugs using the Organization IDs setting (--org-ids / BATON_ORG_IDS). When this list is set, only the specified organizations — and the users, teams, and projects that belong to them — are synced. This prevents duplicate user records that can appear when the same user is a member of more than one Sentry organization with different internal user IDs.

Configure the Sentry connector

To complete this task, you’ll need:

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

Choose how to set up the new Sentry 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 token you generated into the 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 Sentry connector is now pulling access data into C1.

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

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

Search for Baton and click Add.

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

Secrets configuration

# baton-sentry-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-sentry-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Sentry credentials
  BATON_API_TOKEN: <Sentry API token>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

  # Optional: comma-separated list of org IDs or slugs to sync (leave unset to sync all available orgs)
  # BATON_ORG_IDS: my-org-slug,another-org-slug

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

Deployment configuration

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

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

Set up a SentinelOne connector

Set up a ServiceNow connector

⌘I

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Sentry connector

Capabilities

Gather Sentry credentials

Create a Sentry API token

Optional: filter synced organizations

Configure the Sentry connector

Resources

Step 1: Set up a new Sentry connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Gather Sentry credentials

​Create a Sentry API token

​Optional: filter synced organizations

​Configure the Sentry connector

​Resources

​Step 1: Set up a new Sentry connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Sentry credentials

Create a Sentry API token

Optional: filter synced organizations

Configure the Sentry connector

Resources

Step 1: Set up a new Sentry connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector