After adding one or more IdPs to your Jamf Security Cloud account, you can bind them to Activation Profiles as the mechanism to authenticate end users during activation.

The two forms of IdP integrations provided by Jamf Security Cloud are the following:

  • Native

  • Federated

Native IdPs

Native IdPs are those that Jamf can integrate with directly, as illustrated in the following example:

Example: Jamf Security Cloud integrated with Microsoft Entra ID to enable single sign-on (SSO)

Native vendors include:

When a native IdP is configured, users can sign in via SSO through the IdPs user interface. Native integrations also enable advanced IdP capabilities, such as password-less login.

Federated IdPs

For other IdP vendors, Jamf can use IdP Federation via Microsoft Entra ID to enable seamless end user SSO, as illustrated in the following diagram:

IdP Federation support via Microsoft Entra ID

The following IdPs are a selection of those compatible with Jamf via Entra ID federation:

  • Microsoft Active Directory Federation Services (AD FS)

  • Ping Identity

  • OneLogin

  • Auth0

  • Broadcom Identity Security

After you have successfully federated your IdP with Entra ID, you must authorize Jamf in your Entra ID tenant, or provide an authorized Entra ID identity admin with an Entra ID admin consent link to complete this step on your behalf.