Jamf Connect Known Issues

Note:

As part of our ongoing effort to ensure that content we publish is meaningful, the known issues list includes only high-impacting issues that meet the minimum requirements for Jamf Connect.

Login Window

[PI109668] [PI010489] Installing Jamf Connect with the minimum required PingFederate PLIST results in a keychain error message at the login window.
[PI109394] [PI010435] Braille devices fail to transmit data from the Jamf Connect login window when VoiceOver is enabled on computers.
[PI101519] [PI007336] The PostInstall script for Okta configuration does not include the -DefaultJCRight flag necessary for PAM configuration, resulting in the PAM window to log into Oka not appearing and the terminal window erroneously displaying a success message.
[PI105012] [PI008518] In French, some Jamf Connect login text is incorrectly translated.

Menu Bar App

[PI134694] Directory group names obtained via LDAP services no longer appear as intended in the com.jamf.connect.state PLIST after reauthenticating through the Jamf Connect menu bar app. Additionally, Jamf Connect produces a Kerberos-related error in the related log files due to this behavior.
[PI122853] The Jamf Connect menu bar currently produces an error message after a user is successfully promoted to a local administrator when the the optional Verify User Promotion via FIDO2 (VerifyUserPromotionFIDO2) setting is not in use.
Workaround: To temporarily resolve this issue, add the following redirect URI to the Jamf Connect application within your identity provider in addition to the existing redirect URI for Jamf Connect: jamfconnect://loggedin.
[PI123460] Jamf Connect configurations using the Verify User Promotion (VerifyUserPromotion) setting does not allow users to verify their credentials when Windows Integrated Authentication is enabled.
Workaround: To temporarily resolve this issue, enable the optional Verify User Promotion via FIDO2 (VerifyUserPromotionFIDO2) setting and add the following redirect URI to the Jamf Connect application within your identity provider in addition to the existing redirect URI for Jamf Connect: jamfconnect://loggedin.
[PI103023] [PI008951] If you push a Jamf Connect .plist via Jamf Pro with the SignIn dictionary defined, MFA preferences (i.e., automatically push last multifactor option) are not respected by the menu bar app.
[PI102792] The error message displayed when a user enters an incorrect password is non-descriptive.
[PI110486] The Enable Jamf Unlock switch no longer displays at login when Jamf Unlock authentication is enabled in the menu bar app.
[PI103756] [PI009666] When logging in for the first time using Jamf Connect login, users are not prompted to enter a short name shortly after the menu bar app appears. Manually selecting Connect from the menu bar app displays the prompt.
[PI103023] [PI008951] The menu bar app does not respect the Automatically Push Last MFA Method (AutoMFA) preference if the computer was deployed in the PLIST file with Jamf Pro.
[PI103424] [PI009373] Jamf Connect fails to update the preferences window with the short name value given by the user when the The Ask for Short Name (AskForShortName) preference key is configured.

Jamf Connect Configuration

[JC-854] The Create a Separate Local Password checkbox is unchecked by default, but the setting is enabled by default in the Jamf Connect login window.
Workaround: To disable this setting, select and then deselect the checkbox.
[JC-1577] Text entered in the MFA Message setting in the Login tab does not display.
Workaround: Click the </> button to view the entered text for the setting in XML.
[JC-1746] When editing a configuration profile in the XML editor, users can unexpectedly edit the OIDCProvider setting to values that are not supported by Jamf Connect.