Set up a Sumo Logic connector

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

⚠️ This is an early access connector, please test and provide feedback on these docs!

Capabilities

Resource	Sync	Provision
Accounts	✅	✅
Roles	✅	✅

The Sumo Logic connector supports automatic account provisioning.

Gather Sumo Logic credentials

Each setup method requires you to pass in credentials generated in Sumo Logic. Gather these credentials before you move on.

A user whose Sumo Logic permissions include create and manage access keys plus manage users and roles must perform this task.

Look up your API base URL

Based on your your Sumo Logic deployment region, your API base URL will be one of following options:

AU: https://api.au.sumologic.com CA: https://api.ca.sumologic.com DE: https://api.de.sumologic.com EU: https://api.eu.sumologic.com FED: https://api.fed.sumologic.com IN: https://api.in.sumologic.com JP: https://api.jp.sumologic.com KR: https://api.kr.sumologic.com US1 (default): https://api.sumologic.com US2: https://api.us2.sumologic.com

Create an API access key

These instructions create a service account key to be used for the integration. If preferred, you can create and use a personal access key instead.

In the Sumo Logic web interface, navigate to Administration > Security > Service Accounts.
Select a service account (or click + New and create a new service account).
Click Add Access Key.
Give the new key a name, such as “ConductorOne”.
Select the relevant scope:
- To give the key sync-only (READ) permissions: View Users and Roles
- To give the key sync and provision (READ/WRITE) permissions: Manage Users and Roles
Click Save. The new service account key is generated.
Carefully copy and save the Access ID and Access Key.

That’s it! Next, move on to the connector configuration instructions.

Configure the Sumo Logic connector

To complete this task, you’ll need:
The Connector Administrator or Super Administrator role in ConductorOne
Access to the set of Sumo Logic credentials generated by following the instructions above

Follow these instructions to use a built-in, no-code connector hosted by ConductorOne.

In ConductorOne, navigate to Admin > Connectors and click Add connector.
Search for Sumo Logic and click Add.
Don’t see the Sumo Logic connector? Reach out to support@conductorone.com to add Sumo Logic to your Connectors page.
Choose how to set up the new Sumo Logic 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
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.
If you choose someone else, ConductorOne 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.
Enter the API access key’s ID in the API access ID field.
Enter the API access key value in the API access key field.
In the API base URL field, enter the base URL you use for making API calls to Sumo Logic. The default is https://api.sumologic.com.
Optional. If you do not want to sync service account info to ConductorOne, uncheck the Include service accounts checkbox.
Click Save.
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 Sumo Logic connector is now pulling access data into ConductorOne.

Follow these instructions to use the Sumo Logic connector, hosted and run in your own environment.

When running in service mode on Kubernetes, a self-hosted connector maintains an ongoing connection with ConductorOne, automatically syncing and uploading data at regular intervals. This data is immediately available in the ConductorOne UI for access reviews and access requests.

Step 1: Configure the Sumo Logic connector

In ConductorOne, navigate to Connectors > Add connector.
Search for Baton and click Add.
Choose how to set up the new Sumo Logic 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
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.
If you choose someone else, ConductorOne will notify the new connector owner by email that their help is needed to complete the setup process.
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 Sumo Logic connector deployment:

Secrets configuration

# baton-sumo-logic-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-sumo-logic-secrets
type: Opaque
stringData:
  # ConductorOne credentials
  BATON_CLIENT_ID: <ConductorOne client ID>
  BATON_CLIENT_SECRET: <ConductorOne client secret>
  
  # Sumo Logic credentials
  BATON_API_ACCESS_ID: <Sumo Logic API access key ID>
  BATON_API_ACCESS_ID: <Sumo Logic API access key>
  BATON_API_BASE_URL: <Your Sumo Logic API base URL. Default is https://api.sumologic.com.>
  
  # Optional: Include if you do not want to sync service account information
  BATON_INCLUDE_SERVICE_ACCOUNTS: false

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

Deployment configuration

# baton-sumo-logic.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-sumo-logic
  labels:
    app: baton-sumo-logic
spec:
  selector:
    matchLabels:
      app: baton-sumo-logic
  template:
    metadata:
      labels:
        app: baton-sumo-logic
        baton: true
        baton-app: sumo-logic
    spec:
      containers:
      - name: baton-sumo-logic
        image: ghcr.io/conductorone/baton-sumo-logic:latest
        imagePullPolicy: IfNotPresent
        envFrom:
        - secretRef:
            name: baton-sumo-logic-secrets

Step 3: Deploy the connector

Create a namespace in which to run ConductorOne connectors (if desired), then apply the secret config and deployment config files.
Check that the connector data uploaded correctly. In ConductorOne, click Applications. On the Managed apps tab, locate and click the name of the application you added the Sumo Logic connector to. Sumo Logic data should be found on the Entitlements and Accounts tabs.

That’s it! Your Sumo Logic connector is now pulling access data into ConductorOne.