Jamf Pro Cloud
Connection Requirements
1 - Domain
Jamf Cloud instance hostname (e.g., mycompany.jamfcloud.com) or your self-hosted Jamf Pro hostname. Enter without the https:// prefix.
2 - Client ID
The API Client ID generated under Settings -> System -> API Roles and Clients -> API Clients. Sent as client_id in the OAuth2 token exchange.
3 - Client Secret
The API Client secret paired with the Client ID. Jamf displays the secret only once at creation — capture it then. Sent as client_secret in the OAuth2 token exchange.
4 - Fetch users
When enabled, the adapter performs a second pass over the same inventory endpoint with the USER_AND_LOCATION section and emits each unique device-assigned user (default: Disabled). Devices are always fetched.
5 - Aggregate by MAC
When enabled, the adapter falls back to the device's MAC address as the aggregation key if the hostname is missing (default: Enabled). Hostname is always tried first. Disable if MAC duplication across your fleet would create false correlation matches.
6 - Aggregate by IP
When enabled, the adapter falls back to the device's last reported IP address as the aggregation key if both hostname and MAC are unavailable (default: Enabled). Disable in DHCP-heavy environments where IP volatility would produce noisy matches.
7 - Proxy
Optional proxy server in host:port format used to reach Jamf Cloud.
8 - Timeout
The amount of time (in seconds) to wait for Jamf API responses (default: 60). Large tenants can take longer to paginate; raise this if you see timeouts during initial discovery.
Attention
Please perform a connection test to ensure there is a valid connection to your Jamf Pro instance. When the discovery operation is finalized you will be able to see the details on the Assets page.
Last updated