Skip to content
plugboard.appRequest a demo

Connectors

Jamf Pro

Apple device management. The only MDM connector that can populate a loan pool from a smart group.

CategoryMDM
AuthenticationOAuth client credentials
Reacheshttps://yourorg.jamfcloud.com over the internet
Needs an agentNo
Demo modeNo

device.lookupBySerial, device.get, device.sendCommand, device.searchSerial, device.listGroup

These provide:

  • Device details on a repair, resolved from the serial.
  • The device page with live inventory.
  • Remote commands from the device page.
  • Serial autocomplete when registering a loan or lodging a repair.
  • Loan groups auto-populated from a Jamf smart or static group.

Jamf’s modern API uses API roles and clients rather than a user account, so the credential is scoped to what it can do and is not tied to a person who might leave.

  1. In Jamf Pro, go to Settings, System, API roles and clients.
  2. On the API Roles tab, click New.
    • Name it something like Plugboard read.

    • Grant these privileges:

      PrivilegeNeeded for
      Read ComputersDevice lookup and inventory
      Read Mobile DevicesiPads
      Read Smart Computer GroupsLoan pool pull
      Read Static Computer GroupsLoan pool pull
      Send Computer Remote CommandOnly if you want lock, wipe and similar

      Grant the remote command privilege only if you intend to use it.

  3. Save the role.
  4. On the API Clients tab, click New.
    • Name it Plugboard.
    • Assign the API role you just created.
    • Set an access token lifetime. The default is fine.
    • Enable the client.
  5. Click Generate client secret. Copy it immediately. It is shown once.
  6. Note the Client ID as well.

Settings, Connectors, Jamf Pro, Configure.

FieldValue
baseUrlYour Jamf Pro URL, for example https://yourorg.jamfcloud.com
allowDeviceCommandsOptional, off by default. Allow device commands: lock, restart, shut down and check in Macs from the desk

No trailing slash. If your Jamf is on-premises rather than Jamf Cloud, use its hostname. An on-premises Jamf that is not internet-reachable needs a connector agent on a managed deployment.

FieldValue
clientIdThe API Client ID from step 6
clientSecretThe client secret from step 5

Click Save and test. Success reports “Connected to Jamf Pro” with a latency.

  1. In Jamf, create a smart group whose criteria match your loan devices. Most schools use an asset tag prefix, a department, or a building.
  2. In Plugboard, open Settings, Loan groups and edit the group.
  3. Point it at the Jamf group by name.

Devices in the Jamf group are pulled in as available loans, and the pool stays in sync as devices are added and retired.

With allowDeviceCommands on and the matching Send Computer command privileges and “View MDM command information in Jamf Pro API” on the API role, the device page offers lock, restart, shut down and check in for Macs. The setting is off until a connector administrator turns it on.

The Jamf Pro Mobile connector does the same for iPhones and iPads: lock, restart and check in, behind its own allowDeviceCommands setting. Its API role needs Send Mobile Device Restart Device Command, Send Mobile Device Lock Command, View MDM command information in Jamf Pro API and Read Mobile Devices.

  • Wipe is separate. It uses the privileged workflow on the device page, not these commands.
  • Every command is audited, with who sent it, to which device, and the reason where one is asked for.
SymptomCause
401 on testWrong client id or secret, or the client is not enabled in Jamf
Test passes, devices do not resolveThe API role lacks Read Computers, or the serial is not in Jamf
Loan group pull returns nothingThe smart group name does not match, or the role lacks Read Smart Computer Groups
Commands are missing from the device pageallowDeviceCommands is off, the API role lacks the command privileges, or your role lacks device.manage
Works for Macs, not iPadsRead Mobile Devices was not granted
TimeoutsAn on-premises Jamf that the deployment cannot reach. Check with curl from the server

If you do not run Jamf: Intune, Kandji, Mosyle or Chrome Enterprise. All implement the same device capabilities, so the repairs screen does not change. Only Jamf implements device.listGroup for loan pool pull today.