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

  • [PI-007071] The Jamf Connect login window may interrupt incremental macOS updates on Mac computers with T2 chip.
  • [PI-008286] Jamf Connect does not provide the ability to enable Wi-Fi or populate the list of available networks at the login screen if Wi-Fi is disabled.
  • [PI-009301] Jamf Connect fails to display the additional MFA challenge number for Okta's behavior detection policies.
  • [PI-009600] When configured with Okta, the Jamf Connect login window may fail to log in users when their Okta password expiration date is within the range that Okta is configured to send password expiration prompts.

    Workaround: Use local login with Jamf Connect.

  • [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-009119] Jamf Connect fails to get Kerberos tickets upon changing networks.Workaround: Sign in to the menu bar app again.
  • [PI-009255] Jamf Connect fails to change passwords on computers that have previously been bound to an Active Directory domain.

    Workaround: Manually create a krb5.conf file in the /etc/ directory.

  • [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-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-009683] When the Automatically Push Last MFA Method setting is enabled and an Okta user chooses a different MFA method (e.g., Push Verification) than previously used (e.g., Authentication Code) while signing in directly to their Okta dashboard, the Jamf Connect menu bar app continues to automatically push the previously used MFA method (e.g., Authentication Code) rather than the last MFA method used to sign in with Okta.

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.