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.

Bold formatting indicates newly included issues.

The following issues are known in Jamf Connect:

Login Window

  • [PI-007071] The Jamf Connect login window may interrupt incremental macOS updates on Mac computers with T2 chip.

  • [PI-008155] Jamf Connect creates an empty recovery key PLIST file when the EnableFDERecoveryKey and LAPSUser preference keys are both configured.

  • [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-008376] Pressing a key while on the notify screen causes the word "testing" to appear beneath the progress bar.
    Workaround: Use a Jamf Pro policy to demote the user account.

  • [PI-009069] When Bomgar or another application is configured to run on startup, the Jamf Connect login window disappears after 10 to 30 seconds of inactivity.
    Workaround: Press Command + Q to quit the application that is preventing the Jamf Connect login window from displaying or remove the launch daemon causing the issue.

  • [PI-009104] When Jamf Connect allows users to create a separate local password during account creation, Jamf Connect does not respect settings configured via the Passcode payload in an MDM profile.

  • [PI-009139] When configured with the authchanger -preLogin command-line argument, the notify screen incorrectly displays after a user logs in instead of before login.

  • [PI-009151] When the Short Name Attribute (OIDCShortName) setting is configured, Jamf Connect adds the user's network short name as a local account alias rather than the local account username.

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-009010] In environments integrated with Okta and Kerberos, Jamf Connect fails to redirect users to Okta if the domain is not reachable when attempting to change passwords via the menu bar app.

  • [PI-009107] Jamf Connect sometimes uses old credentials to attempt to sign in after a password change when Enable Automatic Sign-in (AutoAuthenticate) is enabled, causing an authentication error.

  • [PI-009119] Jamf Connect fails to get Kerberos tickets upon changing networks.
    Workaround: Sign in to the menu bar app again.

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.

Copyright     Privacy Policy     Terms of Use     Security
© copyright 2002-2020 Jamf. All rights reserved.