# JAMF Software

![Jamf-color.png](https://assets.relyanceuat.xyz/images/docs/34593844064013/34593844056461.png)
Jamf is a mobile device management suite for Apple devices like Macs, iPads, iPhones, and AppleTVs. It empowers IT and security teams to set up and pre-configure new devices, enhancing the user out of box experience (OOBE). Additionally, Jamf can be used to reset, re-purpose, and recover mobile devices and computers.

In order to integrate Jamf with Relyance AI you will need your Jamf **URL**, **Client ID**, **Client Secret**, and follow an **OAuth2** flow.

#### In Jamf:

1. Follow the instructions found here to create a **Client ID** [here](https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/API_Roles_and_Clients.html#ariaid-title3). You'll need an API Role created as a prerequisite to this step. See the instructions [here](https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/API_Roles_and_Clients.html#ariaid-title2).
2. Follow these instructions found here to generate a **Client Secret**[here](https://learn.jamf.com/en-US/bundle/jamf-pro-documentation-current/page/API_Roles_and_Clients.html#ariaid-title4). The required scopes and permissions can be found in the Jamf Integration configuration page in Relyance. Please note, you may not see **Jamf Pro User Accounts & Groups** if you do not have that subscription.
3. The **URL** field will be your JAMF Server URL.

![JAMF.jpg](https://assets.relyanceuat.xyz/images/docs/34593844064013/34593844057485.jpg)

#### In the Relyance AI application:

1. Login to your Relyance AI account.
2. Navigate to the **Settings** (bottom-left corner).
3. Select **Integrations**.
4. Search and locate the **JAMF Software** integration card and click on it.
5. Click on the **Add Connection** button on the top right.
6. Provide a meaningful name for the integration and click on the **Add** button.
7. In the **Overview** section, review the **Scope and Permission**, **Additional Configurations** and **Endpoint** details and click on **Continue**. For more details, see [Integration Features](/docs/introduction-to-relyance-ai/integration-features/).
8. In the **Connection** section, provide the appropriate values and click on **Continue**,
    - **Connection Name**: This property allows you to update the integration specified in Step 6. If you have multiple integrations for the same vendor, you may want to assign distinct names to each. This helps streamline filtering by **Discovery Source** across the **Inventory**, **Visual** **Maps**, **Assets**, and **Data Flow Analysis** pages.
    - **Rescan Frequency**: This property allows you to configure how often Relyance executes scans against this Vendor connection.
    - **Business Atlas Associations** (required): the business entities or products that newly discovered third parties, services and assets from this integration are attributed to. Choose at least one from the **Select Associations** dropdown — the wizard will not advance past this step without one. For more details, see [Business Atlas](/docs/other-settings/business-atlas-overview/).
9. In the **Authentication** section, Please choose the **Authentication Method,** Provide **URL, Client ID** and **Client secret,** click on **Continue**.
10. This step applies only if the **Data Inspection** check box was enabled in Step 7. In the Data Inspection section, provide the appropriate values and click on **Continue**,
    - **Minimum Confidence Level:** This property adjusts the sensitivity of the Data Inspection feature. Lower likelihoods (e.g., Very Low) offer more coverage but may produce false positives, while higher sensitivity (e.g., Very High) provides greater accuracy but less coverage.
11. Review the configuration summary from the **Completion** section and click on **Finish.**

![Screenshot 2025-02-27 at 5.31.10 PM.png](https://assets.relyanceuat.xyz/images/docs/34593844064013/34593805369613.png)

![JAMF_Software_overview_20250224_200022.png](https://assets.relyanceuat.xyz/images/docs/34593844064013/34593844058637.png)

![JAMF_Software_connection_20250224_200024.png](https://assets.relyanceuat.xyz/images/docs/34593844064013/34593805370125.png)

![JAMF_Software_authentication_20250224_200026.png](https://assets.relyanceuat.xyz/images/docs/34593844064013/34593844060301.png)

![JAMF_Software_data_inspection_20250224_200033.png](https://assets.relyanceuat.xyz/images/docs/34593844064013/34593805373453.png)

![JAMF_Software_completion_20250224_200028.png](https://assets.relyanceuat.xyz/images/docs/34593844064013/34593805374221.png)

12. Confirm the integration Status reflects **Connected.**

<!-- auth-methods:begin (generated from the integration catalog; do not hand-edit) -->

## Authentication methods and fields

Pick one of these under **Authentication Method** on the connection wizard's **Authentication** step. This table is generated from the integration catalog, so it always matches what the form actually asks for.

| Method | Required | Optional |
| --- | --- | --- |
| **Client ID/Secret** | `URL`, `Client ID`, `Client secret` (secret) | — |

<!-- auth-methods:end -->

<!-- terraform-examples:begin (generated from the integration catalog; do not hand-edit) -->

## Manage this integration with Terraform

Connections for this integration can be managed as code with the [Relyance Terraform provider](https://registry.terraform.io/providers/Relyance/relyance/latest). Non-secret fields go in `auth.params`; secret fields go in `auth.secrets_wo`, which is write-only — never stored in Terraform state. Rotate secrets by bumping `auth.secrets_wo_version`.

```hcl
resource "relyance_integration_connection" "jamfsoftware" {
  vendor = "jamfsoftware"
  name   = "<your connection name>"

  auth = {
    method = "client-credentials"
    params = {
      server_name = "<server_name>"
      client_id = "<client_id>"
      data_storage_location = "us"
    }
    # Secret fields are write-only: sent to Relyance, never stored in state.
    secrets_wo = {
      client_secret = var.jamfsoftware_client_secret
    }
    secrets_wo_version = 1
  }

  scans = { "data-inspection" = { enabled = true } }
}
```

<!-- terraform-examples:end -->