3 weeks ago
Today we are releasing Jamf Pro 11.18; highlights include:
For additional information on what's included in this release, review the release notes via the Jamf Learning Hub.
To access new versions of Jamf Pro, log into Jamf Account with your Jamf ID. The latest version is located in the Solutions section under Jamf Pro.
Cloud Upgrade Schedule
Your Jamf Pro server, including any free sandbox environments, will be updated based on your hosted data region below. Review this guide if you need assistance identifying the Hosted Data Region of your Jamf Cloud instance.
If you would like to upgrade manually, log in to Jamf Account and select Jamf Pro Info >; click Upgrade on the appropriate instance. Note: This capability is not available for GovCloud environments and is disabled for all instances one day prior to when the scheduled standard upgrades begin.
Subscribe to product alerts to receive real-time updates.
Hosted Region | Begins | Ends |
ap-southeast-2 | 11 July at 1400 UTC | 11 July at 2000 UTC |
ap-northeast-1 | 11 July at 1500 UTC | 11 July at 2300 UTC |
eu-central-1 | 11 July at 2200 UTC | 12 July at 0900 UTC |
eu-west-2 | 11 July at 2300 UTC | 12 July at 0600 UTC |
us-east-1 StateRAMP | 12 July at 0400 UTC | 12 July at 1400 UTC |
us-east-2 | 12 July at 0400 UTC | 12 July at 1400 UTC |
central-us Azure | 12 July at 0500 UTC | 12 July at 0700 UTC |
us-west-2 | 12 July at 0700 UTC | 12 July at 1800 UTC |
Just to clarify, does this mean that in environments that already have SAML authentication (via Entra or some other provider) for SSO configured, we'll be able to both enable the new OIDC backed stuff and still require our technicians sign in using the SSO instead of their personal Jamf accounts? I know that has been a showstopper for many organizations, especially in higher education.
Enable Authentication with Jamf ID Setting
The feature has been added to Settings > Single sign-on > OIDC IdP integration and is enabled by default in environments integrated with OIDC-based SSO in Jamf Account. You can disable this option to force users to use their SSO credentials to log in to Jamf Pro.
@McAwesome customers can maintain their existing SAML authentication for end users while implementing OIDC for administrator access. OIDC authentication is required for admins to access newer platform features like blueprints and compliance.
When OIDC is enabled through Jamf Account, administrators can authenticate using either their federated SSO provider (Entra, in your example) or their Jamf ID. The new toggle in Settings → Single sign-on → OIDC integration provides the additional control of requiring administrators to authenticate exclusively through your preferred SSO provider, preventing the Jamf ID sign-in option.
The new deployment of SelfService+ is really great.
I see this option now on my Jamf Pro.
Do we need to change settings in Settings -> Self Service -> macOS? Should we disable the deployment of the old Self Service app?
@gda you should not need to adjust settings under macOS, they should carry over to Self Service+, but some features will not work in Self Service+. For example, Installation Location, Self Service+ will only be installed in Application folder.
When you turn on Self Service+ deployment, it will stop Self Service classic deployment on the devices that can have Self Service+ on them, no need to disable Self Service classic.
Nice I will need to test but have been using the new SS+.
Our IT team and Security love it.