Known Issues


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

  • [PI-007071] The Jamf Connect login window may interrupt incremental macOS updates on Mac computers with the T2 chip.
  • [PI-010418] When a new FileVault-enabled local account is created with Jamf Connect, the new local account sometimes does not display on the FileVault lock screen after a computer restart.

    Workaround: In Terminal, execute sudo diskutil apfs updatePreboot / and restart the computer.

  • [PI-010435] Braille devices fail to transmit data from the Jamf Connect login window when VoiceOver is enabled on computers.

  • [JC-2368] The Jamf Connect login window does not respect a user's system language settings on Mac computers with Apple silicon.

Menu Bar App

  • [PI-008951] The menu bar app does not respect the Automatically Push Last MFA Method (AutoMFA) preference if the computer was deployed the PLIST file with Jamf Pro.
  • [PI-009262] Jamf Connect does not respect the Hide Home Directory Menu Item (home) preference key if Kerberos is configured and a Kerberos ticket has not yet been retrieved.
  • [PI-009301] Jamf Connect fails to display the additional MFA challenge number for Okta's behavior detection policies.
  • [PI-009359] The menu bar app fails to display the file shares menu item if the Ask for Short Name (AskForShortName) preference is configured and the user does not match case when entering their username.
  • [PI-009360] The menu bar app quits unexpectedly when attempting to sign in if the HomeMount preference key is configured.
  • [PI-009373] 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.
  • [PI-009458] Jamf Connect displays a blank web view and an "application can't be opened" error when attempting to sign in via the menu bar if Okta MFA Enrollment is required.

  • [PI-009943] Jamf Connect crashes when an expired user certificate is stored in the user's macOS login keychain.

  • [PI-009948] When an Okta user becomes locked out of an account mastered by Active Directory, subsequent sign-in attempts in Jamf Connect unexpectedly attempt to obtain Kerberos tickets from the Active Directory domain, which extends the duration of the account lockout.

  • [PI-009997] When integrated with a Kerberos realm, Jamf Connect does not consistently obtain Kerberos tickets when a network change occurs.

  • [PI-010421] 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.
  • [JC-3249] In the Identity Provider tab, the label for the OIDCTenant setting incorrectly displays as ROPG Tenant.

    Workaround: If configuring settings for Azure AD hybrid authentication, make sure the ROPG Tenant setting on the Login tab.

Jamf Unlock

[JC-2658] The Jamf Unlock app does not display some screens correctly when used on an iPad and when the user rotates between between portrait and landscape mode.