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

  • [PI109938] When Jamf Connect is deployed via the InstallEnterpriseApplication command using Jamf Pro's features to automatically deploy it, upon first launch, Jamf Connect looks for an existing keychain item in the context of the _appstore user's home directory, rather than the end user's keychain.
  • [PI109924] Duo MFA and PingID MFA windows that require Webkit do not render properly on devices running macOS12.3.

  • [PI109659] [PI010473] After a computer is logged out and awakened from sleep, Jamf Connect shows a blank screen and end users must use local login.

  • [PI109693] [PI010316] The persistent background window notification causes the Security Agent helper to crash after every successful login.

  • [PI101105] [PI008761] Apple Migration Assistant does not work when Jamf Connect login is installed.

  • [PI103514] [PI009723] Jamf Connect Login does not work correctly with BeyondTrust Remote Support Customer Client.

  • [PI103717] [PI010000] Clicking on an 802.1x EAP-TLS network in the Network Selection pane of the Jamf Connect login window prompts an end user for their username and password then blocks them from joining the network.

  • [PI109797] When the Use Local Authentication by Default (OIDCDefautLocal) preference is set to true, Jamf Connect fails to display shut down and restart buttons at the IdP login window unless the end users selects cancel.

  • [PI104509] [PI010156] Jamf Connect login window does not respect the German QWERTZ keyboard layout.

  • [PI109668] [PI010489] Installing Jamf Connect with the minimum required PingFederate PLIST results in a keychain error message at the login window.

  • [PI100478] [PI007071] The Jamf Connect login window may interrupt incremental macOS updates on Mac computers with a T2 chip.
  • [PI109394] [PI010435] Braille devices fail to transmit data from the Jamf Connect login window when VoiceOver is enabled on computers.

Menu bar app

  • [PI109623] Changing standard users to an admin users under System Preferences > Security and Privacy does not work when using Jamf Unlock.
  • [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.
  • [PI009301] Jamf Connect fails to display the additional MFA challenge number for Okta's behavior detection policies.
  • [PI103452] [PI009360] The menu bar app quits unexpectedly when attempting to sign in if the HomeMount preference key is configured.
  • [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.
  • [PI009997] When integrated with a Kerberos realm, Jamf Connect does not consistently obtain Kerberos tickets when a network change occurs.

  • [PI010421] When MFA is enabled, password verification with OneLogin fails.

    Workaround: Organizations that use OneLogin MFA with the menu bar app should deploy Jamf Connect 2.4.4 or earlier.

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.