Nailing the Security Audit with RRCU

ConductorOne docs

Set up an OpsGenie v2 connector

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

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

Capabilities

  • Sync user identities from Opsgenie to ConductorOne

  • Resources supported:

    • Teams
    • Roles
    • Schedules

Add a new Opsgenie connector

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

  1. In ConductorOne, click Connectors > Add connector.

  2. Search for Opsgenie v2 and click Add.

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

    Do you SSO into Opsgenie using your identity, SSO, or federation provider? If so, make sure to add the connector to the unmanaged Opsgenie app that was created automatically when you integrated your provider with ConductorOne, rather than creating a new managed 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 Opsgenie connector owner must have the following permissions:

    • Connector Administrator or Super Administrator role in ConductorOne
    • Owner or Admin role (or a custom user role with the Edit Configuration user right) in Opsgenie
  1. Click Next.

Next steps

  • If you are the connector owner, proceed to Configure your Opsgenie connector for instructions on integrating Opsgenie 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 Opsgenie connector

A user with the Connector Administrator or Super Administrator role in ConductorOne and Owner or Admin role (or a custom user role with the Edit Configuration user right) in Opsgenie must perform this task.

Step 1: Generate a new API key

  1. Log into Opsgenie and navigate to Profile settings > API key management.

  2. Click Add new API key.

  3. Give the API key a name, such as ConductorOne.

  4. Give the API key Read and Configuration access access rights.

  5. Click Add API key.

  6. The new API key is generated for you. Click Copy.

Step 2: Add your Opsgenie credentials to ConductorOne

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

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

    • Navigate to Connectors > Opsgenie (if there is more than one Opsgenie 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 key you generated in Step 1 into the API key field.

  4. Click Save.

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

Configure the Opsgenie integration using Terraform

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

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