Get the Guide to Modern IGA

ConductorOne Docs

Set up a Sentry connector

ConductorOne provides identity governance for Sentry. Integrate your Sentry instance with ConductorOne to run user access reviews (UARs) and enable just-in-time access requests.

Availability

General availability. The Sentry connector is available to all ConductorOne users.

Capabilities

  • Sync user identities from Sentry to ConductorOne

  • Resources supported:

    • Projects
    • Teams
    • Members
    • Roles

Add a new Sentry connector

This task requires either the Connector Administrator or Super Administrator role in ConductorOne.

  1. In ConductorOne, open Admin and click Connectors > Add connector.

  2. Search for Sentry and click Add.

  3. Choose whether to add the new Sentry connector as a data source to an existing application (and select the app of your choice) or to create a new application.

    Do you SSO into Sentry using your identity provider (IdP)? If so, make sure to add the connector to the Sentry app that was created automatically when you integrated your IdP with ConductorOne, rather than creating a new app.

  1. 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.

    A Sentry connector owner must have the following permissions:

    • Connector Administrator or Super Administrator role in ConductorOne
    • An Admin, Manager, or Owner role in Sentry with the permission to create new integrations
  1. Click Next.

Next steps

  • If you are the connector owner, proceed to Configure your Sentry connector for instructions on integrating Sentry with ConductorOne.

  • If someone else is the connector owner, ConductorOne will notify them by email that their help is needed to complete the setup process.

Configure your Sentry connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and an Admin, Manager, or Owner role in Sentry with the permission to create new integrations must perform this task.

Step 1: Create a new internal integration in Sentry

  1. In Sentry, click Settings > Developer Settings.

  2. Click Create New Integration and select Internal Integration, then click Next.

  3. On the Create Internal Integration page, give your new integration a name, such as ConductorOne.

  4. In the PERMISSIONS section of the page, give the integration the following permissions:

    • Project: Read
    • Team: Read
    • Release: No Access
    • Issue & Event: Read
    • Organization: Read
    • Member: Read
  5. Scroll to the bottom of the page and click Save Changes.

  6. Your new integration is created. Scroll to the TOKENS section of the page and copy the API token that Sentry automatically created for the integration. You’ll need this token in the next step.

Step 2: Add your Sentry credentials to ConductorOne

  1. In ConductorOne, navigate to the Sentry connector by either:

    • Clicking the Set up connector link in the email you received about configuring the connector.

    • Navigate to Admin > Connectors > Sentry (if there is more than one Sentry listed, click the one with your name listed as owner and the status Not connected).

  2. Find the Settings area of the page and click Edit.

  3. Paste the API token you generated in Step 1 into the Token field.

  4. In the Organization slug field, enter your Sentry organization slug.

    • You can find your Sentry organization slug in the URL of your Sentry instance, or on the Organization Settings page.
  5. Click Save.

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

Configure the Sentry integration using Terraform

As an alternative to the integration process described above, you can use Terraform to configure the integration between Sentry and ConductorOne.

See the ConductorOne Sentry integration resource page in the ConductorOne Terraform registry for example usage and the full list of required and optional parameters.