Set up a Seismic connector

Capabilities

The Seismic connector syncs the following resources:

Resource	Sync	Provision
Users
Groups
Roles
Licenses

Content licenses (Business, Premium, Partner) are derived from the SCIM userType field on each user, not from a dedicated API endpoint. License assignment is read-only — license changes typically require admin action in the Seismic console. Users with userType="NonSeismic" (e.g. system or external accounts) hold no content license and receive no license grant.

Gather Seismic credentials

To configure the Seismic connector, you need System Administrator permissions in Seismic.

Go to the Seismic Developer Portal and log in with your admin account. Alternatively, navigate to System Settings > App Registration in the Seismic admin portal.

Click My Apps, then Create New App.

Fill in the app details (name, description) and select Client Credentials as the authentication flow. Seismic implements this as the Client Credentials with User Delegation flow — it is the only client-credentials variant Seismic documents.

Configure the Delegation user selected callback URL on your app. When a tenant admin enables the app and selects the delegated user, Seismic will POST a payload containing delegationUserId to this URL. Your system must store this value — the connector sends it on every token request.

Assign the following scopes to the app registration:

seismic.user.view — required for syncing users, groups, and group members
seismic.user.manage — required for provisioning (create/delete users, grant/revoke group membership and role assignments)
seismic.reporting — required for syncing platform roles

For sync-only deployments, assign seismic.user.view and seismic.reporting. For sync + provisioning deployments, assign all three scopes.

Save the app registration. Copy the Client ID and Client Secret and save them securely. The Client Secret is only shown once.

Have the tenant admin install/enable the app and select the delegated user. Capture the delegationUserId your callback receives — that exact value becomes the connector’s Seismic Delegation User ID configuration field.

Identify your Seismic tenant name (the subdomain from your login URL, e.g., acme if you access acme.seismic.com). The connector uses this to build the OAuth2 token endpoint URL automatically: https://auth.seismic.com/tenants/{tenant}/connect/token.

Configure the Seismic connector

Cloud-hosted
Self-hosted

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

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

Search for Seismic and click Add.

Choose how to set up the new Seismic connector:

Add the connector to a currently unmanaged app
Add the connector to a managed app
Create a new managed app

Set the owner for this connector.

Click Next.

Find the Settings area of the page and click Edit.

Enter the required configuration:

Seismic Client ID: OAuth2 Client ID from the app registration
Seismic Client Secret: OAuth2 Client Secret from the app registration
Seismic Tenant: Your Seismic tenant identifier (used to build the OAuth2 token endpoint URL https://auth.seismic.com/tenants/TENANT/connect/token)
Seismic Delegation User ID: the delegationUserId your app received on the Delegation user selected callback when the tenant admin assigned the delegated user

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

Follow these instructions to use the Seismic 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.

Step 1: Set up a new Seismic connector

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

Search for Baton and click Add.

Choose how to set up the new Seismic connector:

Add the connector to a currently unmanaged app
Add the connector to a managed app
Create a new managed app

Set the owner for this connector.

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.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Seismic connector deployment:

Secrets configuration

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

  # Seismic credentials
  BATON_SEISMIC_CLIENT_ID: <Seismic OAuth2 Client ID>
  BATON_SEISMIC_CLIENT_SECRET: <Seismic OAuth2 Client Secret>
  BATON_SEISMIC_TENANT: <Seismic tenant name>
  BATON_SEISMIC_DELEGATION_USER_ID: <delegationUserId from your callback>

  # Enable provisioning (create/delete users, grant/revoke groups and roles)
  BATON_PROVISIONING: "true"

Deployment configuration

# baton-seismic.yaml
apiVersion: apps/v1
kind: Deployment
metadata:
  name: baton-seismic
  labels:
    app: baton-seismic
spec:
  selector:
    matchLabels:
      app: baton-seismic
  template:
    metadata:
      labels:
        app: baton-seismic
        baton: "true"
        baton-app: seismic
    spec:
      containers:
      - name: baton-seismic
        image: public.ecr.aws/conductorone/baton-seismic:latest
        imagePullPolicy: IfNotPresent
        env:
        - name: BATON_HOST_ID
          value: baton-seismic
        envFrom:
        - secretRef:
            name: baton-seismic-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 Applications. On the Managed apps tab, locate and click the name of the application you added the Seismic connector to. Seismic data should be found on the Entitlements and Accounts tabs.

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

All versions of this connector are available at dist.conductorone.com.

Set up a SAP SuccessFactors SCIM connector

Set up a SentinelOne connector

⌘I

​Capabilities

​Gather Seismic credentials

​Configure the Seismic connector

​Step 1: Set up a new Seismic connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Gather Seismic credentials

Configure the Seismic connector

Step 1: Set up a new Seismic connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector