Today we released Jamf Connect 2.31.0. This release includes the following changes and improvements:
Removal of Support for macOS 11.x
Jamf Connect no longer supports macOS 11.x. Computers with macOS 11.x or earlier will be unable to install Jamf Connect version 2.31.0 or later. Any automatic update workflows configured in your environment will no longer apply.
Other Changes and Improvements
- Users can now enroll their mobile device with Duo Universal Prompt via Okta Identity Engine in the Jamf Connect login window web view.
- Users who authenticate locally with a Kerberos ticket will no longer experience logs that indicate the Kerberos authentication is incomplete prior to beginning network authentication.
Resolved Issues
- [PI112919] The Tenant ID (OIDCTenant) and Custom Okta Authorization Server (OIDCAuthServer) settings now appear as intended when a Jamf Connect login window or menu bar configuration file with these settings configured is imported to Jamf Connect Configuration.
- [PI115038] Login keychains for Okta Classic and Identity Engine users are no longer reset during an expired password reset.
- [PI115176] Jamf Connect .mobileconfig files containing a period in the file name no longer experience unexpected file name changes during an upload to Jamf Pro.
To access new versions of Jamf Connect, log in to Jamf Account with your Jamf ID. The latest version is located in the Products section under Jamf Connect.
Product Documentation
For additional information on what's included in this release, review the release notes via the Jamf Learning Hub.
Thank you!
The Jamf Connect team
