Set up a FleetDM connector

C1 provides identity governance and just-in-time provisioning for FleetDM. Integrate your FleetDM instance with C1 to run user access reviews (UARs) and enable just-in-time access requests.

Capabilities

Resource	Sync	Provision
Accounts
Teams*
Hosts

*Teams support is available only for FleetDM Premium.

The FleetDM connector supports automatic account provisioning and deprovisioning.

Gather FleetDM credentials

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

Here’s the set of credentials you’ll need when setting up the connector:

• FleetDM instance URL
• An API token OR the username and password for your account or for a service account

Note that the user account associated with the API token or the username and password must have the Admin global role in order for all information to be available to the connector. API-only users with the Admin global role are recommended, as the API tokens for these users do not expire.

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

Configure the FleetDM connector

To complete this task, you’ll need:

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

2. Search for FleetDM and click Add.

3. 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.

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

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

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

7. Find the Settings area of the page and click Edit.

8. Select your method of authenticating to Azure DevOps and click either Account credentials or API token.

   If you chose Account credentials:

   1. Enter your email address, FleetDM instance URL, and account password in the relevant fields.

   If you chose API token:

   1. Enter your FleetDM instance URL and API token in the relevant fields.
9. Click Save.

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

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

Self-hosted

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

Step 1: Set up a new FleetDM connector

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

2. Search for Baton and click Add.

3. 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.

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

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

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

7. In the Settings area of the page, click Edit.

8. 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 FleetDM connector deployment:

Secrets configuration

# baton-fleetdm-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-fleetdm-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # FleetDM credentials
  BATON_EMAIL: <Email address for the FleetDM user account>
  BATON_PASSWORD: <Password for the FleetDM user account>
  BATON_INSTANCE_URL: <FleetDM instance URL>
  BATON_TOKEN: <API token for the FleetDM account>

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

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