Capabilities
The Jamf connector syncs the following resources:
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. Created accounts are
Enabled,Full Access, and default to theAuditorprivilege set; a random password is generated and returned once, as plaintext. See Jamf account privileges below for the privileges this requires. - User Groups: Grant/Revoke adds or removes a Jamf user from a static User Group only — Smart User Groups are rejected.
- Sites: Grant/Revoke is only supported for the
userprincipal — a Jamf user’s site membership is a true multi-valued list.userGroup/userAccount/groupsite membership remains sync-only (each of those objects can only belong to one site at a time, so granting a new one would silently displace the old one instead of adding a membership). - Managed Devices: Grant/Revoke sets or clears a device’s
assigneduser (computer or mobile device) — single-valued, so granting to a new user displaces whichever user was previously assigned. Devices with no assignee expose no grantableassignedentitlement. Computers use the Jamf Pro v4 computers-inventory API: Grant overwrites the assignee’s username, name, email, position and phone with the new user’s values (Jamf never auto-populates these for computers), and Revoke clears all five. Mobile devices take these fields from the directory user automatically — Grant only sets the username, and Revoke clears it (and everything Jamf derived from it) by clearing the username. - Groups (Jamf Pro admin account groups): Grant/Revoke a
userAccountwith Group Access only — a Full or Site Access account’s rights come from its own privilege_set, not its groups, so Grant rejects adding one. A group with no members cannot receive its first member through the connector, and Revoke on such a group returns a retryable error instead of reporting success (an ambiguous empty read is never written over, or assumed to mean someone was removed). Do not use Grant/Revoke on directory (LDAP) groups: their membership is managed by the directory and the connector does not detect them. - Roles: Grant/Revoke sets or clears a
userAccountorgroup’s role — the three built-in privilege sets (Administrator,Auditor,Enrollment Only) and every individual privilege are grantable;Customitself is not a role you grant directly. Revoke moves the principal toCustomwith only theRead License Informationprivilege (Jamf’s lowest access, and not itself revocable). Individual privileges can only be granted while the principal is alreadyCustom: revoke the current set first, then grant the individual privileges. Group Access accounts are rejected for Role Grant/Revoke — assign the role to the group instead. Changing a Full or Site Access account’s role removes it from any admin group it belonged to (that membership granted it nothing).
Managed Devices is opt-in. This resource type is off by default in C1 so existing connectors keep working after upgrading. Enable it by selecting the Managed Device resource type in the connector’s sync configuration. Self-hosted runs sync it unless
--sync-resource-types/$BATON_SYNC_RESOURCE_TYPES leaves it out. When enabled, the Jamf account 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.(Optional) Create a service account
The C1 Jamf Pro connector authenticates with either a username and password or a Jamf Pro API client (see below). 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.
(Optional) Create an API client
Instead of a user account, the connector can authenticate with a Jamf Pro API client. See API Roles and Clients in the Jamf documentation.1
In Jamf Pro, go to Settings > System > API roles and clients.
2
On the API Roles tab, create a role with the privileges listed in Jamf account privileges for the capabilities you plan to use.
3
On the API Clients tab, create a client, assign it the role, and enable it.
4
Click Generate client secret, then copy the client ID and the client secret. Jamf shows the secret only once.
Jamf account privileges
The Administrator privilege set covers everything. For least privilege, grant:Read Accounts/Create Accounts/Update Accounts/Delete Accounts cover both admin user accounts and admin groups — Jamf has no separate privilege for account groups. Every write path reads the object first, so each Update privilege above needs its Read counterpart too.
Jamf reports a missing privilege differently depending on which API it uses: the Classic API (/JSSResource — Users, Accounts, Static User Groups) answers with HTTP 401, and the Jamf Pro API (/api/v1, /api/v2, /api/v4 — the roles catalog, Computers, Mobile Devices) with HTTP 403. The connector reports both as a permission error.
Configure the Jamf connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your Jamf connector is now pulling access data into C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for Jamf 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
Choose an authentication method and enter its fields:
- Username and password (default):
- 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.
- API client:
- API Client ID: The client ID of the API client you created.
- API Client Secret: The client secret of that API client.
- Instance URL: The base URL of your Jamf Pro instance, including
https://(for examplehttps://yourcompany.jamfcloud.com). - 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.
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.