Set up a Jamf connector

ConductorOne provides identity governance and just-in-time provisioning for Jamf Pro. Integrate your Jamf Pro instance with ConductorOne to run user access reviews (UARs), enable just-in-time access requests, and automatically provision and deprovision Jamf accounts.

Capabilities

The Jamf connector syncs the following resources:

Resource	Sync	Provision
Users		Create, Delete
User Accounts		Create, Delete
Groups
User Groups
Roles
Sites
Managed Devices

Notes:

• Jamf has two distinct account types: Users (directory users) and User Accounts (Jamf Pro console admins). The connector can only create one of these types per connector instance — set by the Account Provisioning Target configuration field. Deletion works for both types regardless of this setting.
• Groups, User Groups, Roles, and Sites are synced for visibility (including membership) but are not provisionable — access changes to these resources must be made directly in Jamf Pro.
• When creating a User Account, the privilege_set profile field sets its access level (Administrator, Auditor, Enrollment Only, or Custom). For Custom, at least one of privileges_jss_objects, privileges_jss_settings, privileges_jss_actions, privileges_recon, privileges_casper_admin, privileges_casper_remote, or privileges_casper_imaging must be set to a list of Jamf privilege names — Jamf validates these names server-side, not the connector.

Managed Devices is opt-in. This resource type is off by default so existing connectors keep working after upgrading. Enable it by selecting the Managed Device resource type in the connector’s sync configuration. When enabled, the Jamf API role used by the connector must additionally have the Read Computers and Read Mobile Devices privileges, or the sync will fail.

Gather Jamf credentials

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

A user the Administrator role in Jamf Pro must perform this task.

(Optional) Create a service account

The C1 Jamf Pro connector requires a username and password. If desired, you can set up a service account to be used for the connector.

1. Follow the instructions in the Jamf documentation for Creating a Jamf Pro User Account

2. Give the user you create full access to the Jamf Pro instance and the Administrator privilege set.

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

Configure the Jamf connector

To complete this task, you’ll need:

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

3. Choose how to set up the new Jamf 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 the required configuration:

   • Instance URL: The URL of your Jamf Pro instance.
   • Username: The username of the service account you created (or the username of a Jamf Pro user with Administrator permissions).
   • Password: The password associated with the username.
   • Account Provisioning Target (optional): Which Jamf account type ConductorOne should create when provisioning accounts — user (default) creates directory users, userAccount creates Jamf Pro console admin accounts. Only one type can be created at a time per connector instance.
8. Click Save.

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

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

Self-hosted

Follow these instructions to use the Jamf 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.
• Download center: Pre-built binaries for baton-jamf.

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

Secrets configuration

# baton-jamf-secrets.yaml
apiVersion: v1
kind: Secret
metadata:
  name: baton-jamf-secrets
type: Opaque
stringData:
  # C1 credentials
  BATON_CLIENT_ID: <C1 client ID>
  BATON_CLIENT_SECRET: <C1 client secret>
  
  # Jamf credentials
  BATON_INSTANCE_URL: <URL of your Jamf Pro instance>
  BATON_PASSWORD: <Password to the Jamf Pro account>
  BATON_USERNAME: <Username for the Jamf Pro account>

  # Optional: only needed if provisioning accounts. Defaults to "user".
  # BATON_CREATE_ACCOUNT_RESOURCE_TYPE: <"user" or "userAccount">

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

To provision accounts (create/delete) in self-hosted mode, the deployment also needs BATON_PROVISIONING: "true" set — see the Deployment configuration below.

Deployment configuration

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

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

You can find pre-built binaries for baton-jamf on the ConductorOne download center.