Set up a Coupa connector

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

Capabilities

Resource	Sync	Provision
Accounts
Account Groups ¹
Groups
Roles
Licenses

¹ Account Groups sync is opt-in. To enable it, select Account Groups in the resource types to sync when configuring the connector in C1, and ensure the core.accounting.read OAuth scope is added to your Coupa OAuth client.

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 user account in Coupa, allowing them to access the system
disable_user	user_id (string, required)	Disables an active user account in Coupa, preventing them from accessing the system

Gather Coupa credentials

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

A user with Admin access in Coupa must perform this task.

Look up your Coupa domain

1. Log into your Coupa control panel and copy the URL from your browser.

Create an OAuth app

1. In the Coupa control panel, click Setup.

2. Search for “OAuth” and click OAuth2/OpenID Connect Clients.

3. Click Create to create a new OAuth app.

4. Fill out the OAuth app creation form as follows:

   • Select Grant type Client credentials.
   • Give your app a name, such as C1.
   • Leave JWKS URI field blank.
   • Enter the appropriate login and contact information for your organization.
   • Select scopes:

   You’ll need these scopes to give C1 READ access (syncing access data):

   • core.business_entity.read
   • core.common.read
   • core.user_group.read
   • core.user.read
   • email
   • login
   • openid
   • profile

   If you also want to sync Account Groups, add:

   • core.accounting.read

   You’ll need these scopes to give C1 READ/WRITE access (syncing access data and provisioning access):

   • core.business_entity.read
   • core.business_entity.write
   • core.common.read
   • core.common.write
   • core.user_group.read
   • core.user_group.write
   • core.user.read
   • core.user.write
   • email
   • login
   • openid
   • profile

   If you also want to sync and provision Account Groups, add:

   • core.accounting.read
5. At the bottom of the page click Save.

Look up your new OAuth app’s credentials

1. Open the OAuth2 app you just created.

2. Copy and save the Identifier string. This is your client ID.

3. Click Show/Hide to view your client secret. Copy and save the client secret.

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

Configure the Coupa connector

To complete this task, you’ll need:

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

3. Choose how to set up the new Coupa 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. Enter your Coupa domain in the Domain field.

8. Paste the client ID into the Client ID field.

9. Paste the client secret into the Client secret field.

10. Click Save.

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

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

Self-hosted

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

• Official download center: For stable binaries (Windows/Linux/macOS) and container images.

• GitHub repository: Access the source code, report issues, or contribute to the project.

Step 1: Set up a new Coupa 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 Coupa 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 Coupa connector deployment:

Secrets configuration

# baton-coupa-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-coupa-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Coupa-specific credentials
  BATON_COUPA_CLIENT_ID: <Coupa client ID>
  BATON_COUPA_CLIENT_SECRET: <Coupa client secret>
  BATON_COUPA_DOMAIN: <Coupa domain>

  # Optional: include if you want C1 to provision access using this connector
  BATON_PROVISIONING: true

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

Deployment configuration

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

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