Jamf Security Cloud manages the identity provider (IdP) and Jamf Connect client information to create a connection between Jamf Trust for macOS URL Schemes and Jamf Connect.
Jamf Connect 2.30.0 or later
For configurations using Jamf Connect 3.0.0 or later, Self Service+ 2.0.0 or later is also required to configure Zero Touch App Activation.
Jamf Trust for macOS 2.21.0 or later
- An existing app registration and its resulting client ID for the Jamf Connect for macOS app in Microsoft Entra ID or Okta Identity Engine.Note:
Zero Touch App Activation only supports Microsoft Entra ID and Okta Identity Engine as a cloud identity provider (IdP). Support for additional IdPs will be available in future releases of Jamf Trust for macOS.
For more information, see Integrating Jamf Connect with Microsoft Entra ID or Integrating Jamf Connect with Okta.
Access to your Jamf Security Cloud portal and permission to link an IdP.
For more information, see Authorizing Jamf Security in your Microsoft Entra tenant ID or Authorizing Jamf Trust in Your Okta Organization.
An existing Jamf Connect configuration profile.
For more information, see Jamf Connect Configuration.
Access to your Microsoft Entra ID or Okta Identity Engine portal
An activation profile and the Jamf Trust app distributed on managed computers.
For more information, see Creating an Activation Profile for Zero Trust Network Access and Distributing the Jamf Trust App to macOS using Jamf Pro.
Jamf Security Cloud can now relay the necessary information between Jamf Connect and Jamf Trust.
The use of an optional UEM integration will allow Jamf Pro to send device inventory and group data to Jamf Security Cloud. For more information, see UEM Connect for Jamf Security Cloud.