Set up a Sumo Logic connector

Capabilities

Resource	Sync	Provision
Accounts
Roles

The Sumo Logic connector supports automatic account provisioning and deprovisioning.

Connector actions

Connector actions are custom capabilities that extend C1 automations with app-specific operations. You can use connector actions in the Perform connector action automation step.

Action name	Additional fields	Description
enable_user	`user_id` (string, required)	Enables a disabled Sumo Logic user account
disable_user	`user_id` (string, required)	Disables an active Sumo Logic user account

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: 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 “C1”.

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.

Done. 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 C1
Access to the set of Sumo Logic 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 Apps > Connectors and click Add connector.

Search for Sumo Logic and click Add.

Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

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 C1, uncheck the Include service accounts checkbox.

Optional. In the Minimal access role name field, enter the name of a low-privilege role that should be automatically assigned to an account when their last role is revoked during provisioning operations. The default is Analyst.

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 Sumo Logic connector is now pulling access data into C1.

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 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: Configure the Sumo Logic connector

In C1, navigate to Apps > Connectors and click Add connector.

Search for Baton and click Add.

Set the connector’s Name and, optionally, a Description.

Click the pencil icon next to Owners to choose who can configure and manage this connector.

Click Add. The connector is created and its configuration page opens.

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:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 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.>
  BATON_MINIMAL_ACCESS_ROLE_NAME: <The Sumo Logic role that accounts will be assigned if all other roles are revoked. Default is Analyst.>

  # Optional: Include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true
  
  # 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: public.ecr.aws/conductorone/baton-sumo-logic:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-sumo-logic
        envFrom:
        - secretRef:
            name: baton-sumo-logic-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 Sumo Logic connector to. Sumo Logic data should be found on the Entitlements and Accounts tabs.

Done. Your Sumo Logic connector is now pulling access data into C1.

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Sumo Logic connector

Capabilities

Connector actions

Gather Sumo Logic credentials

Look up your API base URL

Create an API access key

Configure the Sumo Logic connector

Resources

Step 1: Configure the Sumo Logic connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Connector actions

​Gather Sumo Logic credentials

​Look up your API base URL

​Create an API access key

​Configure the Sumo Logic connector

​Resources

​Step 1: Configure the Sumo Logic connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Connector actions

Gather Sumo Logic credentials

Look up your API base URL

Create an API access key

Configure the Sumo Logic connector

Resources

Step 1: Configure the Sumo Logic connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector