Hey everyone - with Jamf Pro 11.13 we introduced the ability to manage your SSO authentication configuration in Jamf Account, and then re-use that configuration for managing access to Jamf Pro. Centralizing the authentication management for SSO in Jamf Account allows multiple Jamf applications and services to share in the same login process and eliminates the need for necessarily setting up IdP connection within each service. Using the settings for SSO from Jamf Account enables authentication through your organization's preferred identity provider, but for organizations without an IdP, the integration allows for Jamf ID to act as your means of authentication.
With the release of Jamf Pro 11.15, the first of several new services appeared: blueprints. The blueprints feature takes advantage of a new platform architecture that enables Jamf to update services in a way that isn't tied to Jamf Pro releases. Part of enabling these new services is a requirement for a Jamf Pro tenant to adopt the SSO with OIDC integration from Jamf Account. The SSO integration again provides individuals in an organization with a consistent login experience across Jamf application, but is also critical in enabling access to these features for the individual. Individual organizations (and tenants) can require log in with federated authentication to their chosen IdP or Jamf ID.
We've heard your feedback Jamf Nation, and we collected some of the frequently asked questions as well as some plans for enabling more organizations to adopt this SSO integration. We're not done yet, but I encourage teams to read our blog post on the updates and continue to share your feedback with us. I appreciate your time!
