Jamf Connect 2.3.0 Beta Now Available


Hi Jamf Nation,

The Jamf Connect 2.3.0 beta includes the following enhancements and bug fixes.

Changes to Identity Provider Discovery Endpoint Usage
Jamf Connect now detects and uses any discovery URLs that are included in a Jamf Connect configuration profile instead of using the pre-configured discovery URLs that are included in Jamf Connect’s authentication framework by default.

To ensure authentication with Jamf Connect continues to succeed, make sure you do the following before you deploy Jamf Connect 2.3.0:

  • If you are using an identity provider other than PingFederate or a custom option, make sure discovery URL key-value pairs are either not configured (Jamf Connect uses pre-configured discovery URLs for supported IdPs) or match the discovery endpoint documented by your IdP.
  • If you use Jamf Connect with Azure AD in an AD FS hybrid identity environment, in addition to making sure the Discovery URL (OIDCDiscoveryURL) is not configured, make sure the Hybrid ID Discovery URL (ROPGDiscoveryURL) uses your AD FS discovery endpoint.

Keyboard Layout Selection at the Login Window
Users can now select a keyboard type from the Jamf Connect login window by clicking the keyboard button in the upper-right of the screen. Users can select from any keyboard input source supported by macOS. This feature also fixes PI-009230.

Bug Fixes
Jamf Connect 2.3.0 includes the following bug fixes:

  • [PI-009139] Fixed an issue that caused the authchanger -preLogin command-line argument to incorrectly display the Notify screen after a user logs in instead of before login.
  • [PI-009274] Fixed an issue that caused Jamf Connect to not provide an option to complete unsupported MFA request types when attempting to log in.
  • [PI-009295] The Jamf Connect launch agent package is now built as a universal installer package.
  • [PI-008572] Jamf Connect fails ROPG authentication when configured with Okta via an OpenID Connect authentication protocol rather than the Okta Authentication API.
  • [PI-009373] Jamf Connect fails to update the menu bar Preferences window with the short name value given by the user when the The Ask for Short Name (AskForShortName) preference key is configured.
  • [JC-2526] When a user logs out on computers with macOS 11.0-11.2.0 that are FileVault-enabled, the Jamf Connect login window does not display and logout fails.

How to join the beta :
If you would like to participate in the beta program, please enroll using the Beta Programs tab on Jamf Nation under My Assets within the account section. After enrollment, reference our Release Notes for a complete list of what is included in the beta build.

Remember, this is a beta release. We strongly encourage you to install this software in a non-production environment.

As always, the beta program is operated under non-disclosure, so please do not share any information regarding your testing on any public forum, including the non-beta sections of Jamf Nation. Use the Jamf Nation beta discussion area or contact Jamf via beta@jamf.com with any questions regarding the beta.

Thank you to all those who participate in the program!