Set up a Brex connector

Capabilities

The Brex connector syncs the following resources:

Resource	Sync	Provision
Accounts
Departments
Locations
Titles

Account entitlements. Accounts carry no entitlements of their own — a user’s access is expressed as grants against Departments, Locations, and Titles. When all three are excluded from the sync, the connector skips the account grant pass as well, since the resources those grants point at wouldn’t be present.

Actions

The Brex connector supports the following account actions:

Action	Description
Enable User	Sets a user’s status to `ACTIVE`
Disable User	Sets a user’s status to `DISABLED`

Gather Brex credentials

To configure the Brex connector, you need administrator permissions in Brex.

Navigate to the Brex admin console or API settings.

Create API credentials for C1:

Create a new API key or token named C1
Grant the required scopes or permissions
Copy the credentials and save them securely

Configure the Brex connector

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 Brex 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 required configuration:

API Key: Your Brex API key

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

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

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 Brex connector

In C1, navigate to Apps > Connectors > 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.

Step 2: Create Kubernetes configuration files

Create two Kubernetes manifest files for your Brex connector deployment:

Secrets configuration

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

  # Brex credentials
  # Add connector-specific credentials here

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

Deployment configuration

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

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

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

Welcome

Manage connectors

Deploy connectors

Upload connector data

Configurable connectors

Pre-built connectors

Set up a Brex connector

Capabilities

Actions

Gather Brex credentials

Configure the Brex connector

Resources

Step 1: Set up a new Brex connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector

​Capabilities

​Actions

​Gather Brex credentials

​Configure the Brex connector

​Resources

​Step 1: Set up a new Brex connector

​Step 2: Create Kubernetes configuration files

​Secrets configuration

​Deployment configuration

​Step 3: Deploy the connector

Capabilities

Actions

Gather Brex credentials

Configure the Brex connector

Resources

Step 1: Set up a new Brex connector

Step 2: Create Kubernetes configuration files

Secrets configuration

Deployment configuration

Step 3: Deploy the connector