Set up an Atlassian Opsgenie connector

C1 provides identity governance for Opsgenie. Integrate your Opsgenie instance with C1 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 connector with C1 for the first time, you’re in the right place.

Capabilities

Resource	Sync	Provision
Accounts
Teams
Roles
Schedules

Gather Opsgenie credentials

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

Important

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

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

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. Carefully copy and save the API key.

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

Configure the Opsgenie connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• Access to the set of Opsgenie 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 Integrations > Connectors and click Add connector.

2. Search for Opsgenie 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 C1)
   • Add the connector to a managed app (select from the list of existing managed apps)
   • Create a new managed app
4. 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.

5. Click Next.

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

7. Paste the API key into the API key field.

8. Click Save.

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

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

Self-hosted

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

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

2. Search for Baton 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 C1)
   • Add the connector to a managed app (select from the list of existing managed apps)
   • Create a new managed app
4. 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.

5. Click Next.

6. In the Settings area of the page, click Edit.

7. 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 Opsgenie connector deployment:

Secrets configuration

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

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

Deployment configuration

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

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