Jamf Pro device sync
Airgate reads the Macs and the iPhones and iPads that Jamf Pro manages and writes their state (managed, OS, model, owner, FileVault…) to the matching device records. Jamf Pro has no page of its own under Integrations: it is configured as a context server of type Jamf Pro on Settings › Webhooks.
How it works
Section titled “How it works”- Every sync interval (default every hour) Airgate pages through the Jamf
Pro API, 200 records per page:
- computers:
/api/v1/computers-inventory(sections general, hardware, operating system, user and location, disk encryption); - mobile devices:
/api/v2/mobile-devices/detail(older Jamf Pro versions:/api/v2/mobile-devices).
- computers:
- Matching by MAC. Computers are written to the device records of their
macAddressandaltMacAddress; mobile devices to their Wi-Fi MAC (and Bluetooth MAC). - Devices that leave Jamf get
MDM Enabled = falseandMDM Compliant = false.
Before you begin
Section titled “Before you begin”- A Jamf Pro account that can create API roles and clients.
- An Airgate administrator with
admin:write. - Airgate reaches your Jamf Pro URL (for example
https://contoso.jamfcloud.com) over HTTPS.
Step 1: Create an API client in Jamf Pro
Section titled “Step 1: Create an API client in Jamf Pro”- In Jamf Pro, open Settings › System › API roles and clients.
- On API Roles, create a role
Airgate readwith the privileges Read Computers and Read Mobile Devices. - On API Clients, create a client
Airgate, assign the role, enable it, and select Generate client secret. - Copy the Client ID and the Client secret.
Airgate can also log in with a Jamf Pro user name and password (basic
authentication, exchanged for a token at /api/v1/auth/token). An API
client is recommended.
Step 2: Add the Jamf Pro context server in Airgate
Section titled “Step 2: Add the Jamf Pro context server in Airgate”-
Open Settings › Webhooks, select the Context servers tab and Add context server.
-
Choose the type Jamf Pro.
-
Fill in:
Field Value Name Jamf ProBase URL https://contoso.jamfcloud.comAuthentication OAuth2 client credentials (default) or Basic / user + password Client ID / Client secret from Step 1 (stored encrypted). The token URL defaults to <Base URL>/api/oauth/token.Synchronise devices (MDM poller) on Sync interval (minutes) 5 to 10,080 (default 60) Poll computers, Poll mobile devices on (default) or off -
Save, then select Test connection on the server row. A success shows “Jamf Pro inventory API reachable”.
The Integrations tab of the same page lists the server under MDM with its last run, next run, devices and updated counts. Synchronised devices lists what was synced.
Step 3: Use Jamf data in access policies
Section titled “Step 3: Use Jamf data in access policies”Jamf writes the generic MDM attributes. Add conditions on them to a rule
through the API (/api/v1/t/{tenant}/enforcement-policies), for example:
| When | Then |
|---|---|
Endpoint:MDM Enabled EQUALS true and Endpoint:MDM Source CONTAINS Jamf |
Allow, corporate VLAN |
Endpoint:Encryption Enabled EQUALS false |
Remediation VLAN |
Attributes written
Section titled “Attributes written”| Attribute | Computers | Mobile devices |
|---|---|---|
MDM Enabled |
managed state (true / false) |
managed state |
MDM Compliant |
managed state | managed state |
MDM Identifier, MDM Device Name |
Jamf ID, name | Jamf ID, display name |
OS, OS Version |
for example macOS, 15.1 |
device type (iOS…), version |
Model, Manufacturer, Serial Number |
hardware (Apple) |
hardware (Apple) |
Owner |
user name or e-mail from user and location | user name or e-mail |
Encryption Enabled |
true when FileVault 2 is ENCRYPTED |
— |
Last Check In |
last contact time | last inventory update |
MDM Source |
Jamf: <server name> |
Jamf: <server name> |
Jamf has no compliance state of its own: MDM Compliant follows the managed
flag.
Verify
Section titled “Verify”- Settings › Webhooks › Integrations: the Jamf server under MDM with Last run succeeded and a device count.
- Devices › Devices › a Mac’s MAC › Attributes:
MDM Source=Jamf: Jamf Pro.
Troubleshooting
Section titled “Troubleshooting”| Symptom | Cause | Fix |
|---|---|---|
Test or sync: jamf returned HTTP 401 |
Wrong client ID or secret, or the client is disabled. | Check the API client in Jamf Pro. |
Sync: jamf /api/v1/computers-inventory HTTP 403: … |
The API role lacks Read Computers. | Add the privilege to the API role. |
Sync: jamf /api/v2/mobile-devices/detail HTTP 403: … |
The API role lacks Read Mobile Devices. | Add the privilege, or turn off Poll mobile devices. |
MDM returned no devices; keeping the N known devices … |
Jamf returned an empty inventory. | Check the API role. To accept an empty inventory, turn on Accept an empty inventory. |
| A Mac is not matched | It joins the network with another adapter (USB or dock Ethernet). | Allow it by another rule, or use certificates. |