Set up a Ramp connector

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

Capabilities

Resource	Sync	Provision
Accounts
Roles
Vendors

Vendor owner is single-assignee. Each Ramp vendor can have only one owner at a time. Granting the vendor owner entitlement to a new user overwrites the previous owner in Ramp — the prior owner is silently removed. Revoking the entitlement clears the owner only when the principal being revoked is the current owner.

The Ramp connector supports automatic account provisioning.

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
disable_user	user_id (string, required)	Deactivate a Ramp user. The user will no longer be able to log in, spend on cards, or receive notifications.
enable_user	user_id (string, required)	Reactivate a Ramp user. The user can log in to Ramp again, spend on their previously issued cards, and resume receiving notifications.

Configure the Ramp connector

To complete this task, you’ll need:

• The Connector Administrator or Super Administrator role in C1
• The Administrator role in Ramp

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 Ramp and click Add.

3. Choose how to set up the new Ramp 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. Click Login with OAuth.

8. Log in and authorize C1 with your Ramp instance.

9. You will then be redirected back to the Ramp setup page in C1, where you’ll see an authorization message.

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

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

Self-hosted

Follow these instructions to use the Ramp 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 Ramp 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 Ramp 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 Ramp connector deployment.

The Ramp connector supports two authentication methods — pick one when populating the secret:

• Access Token — a long-lived Ramp API access token.
• OAuth 2.0 Client Credentials — a Ramp OAuth client ID and secret (the connector exchanges them for a short-lived access token automatically, via https://api.ramp.com/developer/v1/token).

See the Ramp authorization docs for how to create an OAuth app with the Client Credentials grant type and users:read, users:write, vendors:read, and vendors:write scopes.

The connector points at https://api.ramp.com by default. Set BATON_RAMP_BASE_URL (or the Ramp API Base URL field) to https://demo-api.ramp.com (or another Ramp environment) to override.

Secrets configuration

Option A — Access Token:

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

  # Ramp credentials
  BATON_TOKEN: <Ramp API token>

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

Option B — OAuth 2.0 Client Credentials:

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

  # Ramp OAuth credentials
  BATON_RAMP_CLIENT_ID: <Ramp OAuth client ID>
  BATON_RAMP_CLIENT_SECRET: <Ramp OAuth client secret>

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

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