# Jamf Pro

Connect Jamf Pro to Risotto to manage Apple devices directly from Slack conversations

The Organization-wide integration between Risotto and Jamf Pro provides access to five workflow tools that let teams manage devices directly from Slack conversations via Jamf Pro's MDM platform.

## Prerequisites

To setup your integration, you will need:

- Access to your Jamf Pro tenant
- The Org Admin or Manager role in Risotto
- Administrative privileges in Jamf Pro to [create and manage API roles](https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-11.25.0/page/API_Roles_and_Clients.html)
- A generated client ID and secret from Jamf Pro
- Your Jamf Pro server URL

### Roles and Scopes Required

- **Read Computers** - View computer information
- **Read Computer Extension Attributes** - View extended attributes
- **Send Computer Remote Lock Command** - Lock devices (only if you use the lock tool)
- **View MDM command information in Jamf Pro API** - Send lock commands (only if you use the lock tool)
- **View Disk Encryption Recovery Key** - Access FileVault keys (only if you use the FileVault key tool)

The Assistant can also build [script tools](https://www.tryrisotto.com/docs/integrations/tools/script-tools#connection-auth-http-without-a-secret) that call the Jamf Pro API through this connection. Add the privileges that those calls need to the same API role.

## Setup

In the JAMF Pro web console:

1. Navigate to **Settings > System > API Roles and Clients**.
2. Create a new API Role with the following privileges:
   - **Read Computers** - View computer information
   - **Read Computer Extension Attributes** - View extended attributes
   - **Send Computer Remote Lock Command** and **View MDM command information in Jamf Pro API** - Lock devices (if needed)
   - **View Disk Encryption Recovery Key** - Access FileVault keys (if needed)
3. Create a new API Client:
   - Give it a descriptive display name (e.g., "Risotto")
   - Assign the API Role you created
   - Set an appropriate access token lifetime
4. Click **Generate Client Secret** and copy both the **Client ID** and **Client Secret**.
5. Note your JAMF Pro server URL (e.g., `https://yourcompany.jamfcloud.com`). It must start with `https://`. Risotto does not save an `http://` URL, because it would send the client secret without encryption.

In Risotto:

1. **Open the Jamf integration**

   Go to **Settings > Integrations** and click the **Jamf** card. On the **API client** card, click **Connect**.

   *Product example: Jamf's integration page in Settings, not connected, with Connect on the API client card ringed.*

2. **Enter your Jamf Pro details**

   In the **JAMF Pro** dialog, enter your **Server URL** (a full URL, such as `https://yourcompany.jamfcloud.com`) and paste the **Client ID** and **Client Secret**. Then click **Save**.

   *Product example: The JAMF Pro setup dialog filled in with Northwind's server URL, client ID and client secret, with Save ringed.*

   Risotto shows "JAMF Pro settings saved", and the **API client** card shows **Connected** with your server URL and client ID.

## Troubleshooting

### Locking a device fails with HTTP 403

Risotto sends the lock as a Jamf Pro API MDM command. This needs two privileges on the API Role: **Send Computer Remote Lock Command** and **View MDM command information in Jamf Pro API**. An API Role made from older setup steps has only the first one. The lock tool then answers "Failed to lock \<device>. JAMF Pro denied the lock command (HTTP 403)." and names both privileges, and your admins get one alert about it.

Add **View MDM command information in Jamf Pro API** to the API Role in Jamf Pro. You do not need a new client secret.

### Admins get a JAMF Connection Error alert

Jamf Pro refused Risotto's credentials (HTTP 401) or its privileges (HTTP 403). The alert lists the usual causes: an expired or deleted client secret, a wrong server URL, or a network problem. Risotto sends the alert once for each error, not once for each failed call.

Check the API Client and its API Role in Jamf Pro, then save the Jamf settings again in Risotto. Saving the settings clears the error.

The alert also comes when the saved server URL starts with `http://`. Risotto calls Jamf Pro over HTTPS only, so every Jamf tool fails with "The org's Jamf Pro server URL uses http, and Risotto calls Jamf Pro over https only." Change the **Server URL** to `https://` and save.

### Self-hosted Jamf Pro servers

Risotto reads your server's Jamf Pro version before its first device lookup. From Jamf Pro 11.30, it uses the current computer inventory endpoints. An older server keeps the endpoints that it supports, so you do not have to upgrade to connect.

If you need additional assistance with this integration, contact your Risotto CSM.

Source: https://www.tryrisotto.com/docs/integrations/device-management/jamf-pro
