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.

Jamf Connect Login

The following issues are known in Jamf Connect Login:

  • [PI-006872] The Jamf Connect login window is not centered on-screen when the computer is connected to an external monitor.

  • [PI-007042] Sudo authentication with the pluggable authentication module (PAM) fails when integrated with Microsoft Azure AD.

  • [PI-007101] When using Google ID for authentication, a prompt for new users who are required to enroll in multi-factor authentication (MFA) is not displayed.

  • [PI-007225] Jamf Connect Login uses the "groups" attribute in the user's ID token by default for all cloud identity providers (IdPs) when determining if a user should be created as a local admin.
    Workaround: Use the OIDCAdminAttribute preference key to change the ID token attribute used to create local admins as needed. If your IdP is Microsoft Azure AD, for example, set this key to "roles".

  • [PI-007246] After changing their network password in the Azure Portal, users are not prompted to update their local account password to match their new network password during their next log in, which may fail.
    Workaround: Log in with local authentication, if enabled, using the old password, and then allow Jamf Connect Verify to sync the network and local passwords.

  • [PI-007254] When integrated with Okta, login may fail when user migration is enabled with a one-time password (OTP) MFA method.

  • [PI-007341] When PAM authentication and Duo MFA are enabled for Okta users, the Duo MFA window does not correctly display.

  • [PI-007465] After using Google Cloud ID to create a local user account, users are unable to log in after their first log out.
    Workaround: Remove the DenyLocal key from your Jamf Connect Login configuration profile and only use local login.

  • [PI-007469] Jamf Connect Login is unable to create a Jamf Connect Sync or Jamf Connect Verify keychain item for already existing users.

  • [PI-007478] On start up, the Jamf Connect login window may not load and display the following message: "Error: could not create request URL"
    Workaround: Wait several minutes for the computer to establish a network connection and click Refresh.

  • [PI-007513] When SMS or a Yubikey is enabled as an MFA method with Okta, Jamf Connect Login displays an unexpected error. If used during user creation, the new local user account is created without a password.

Jamf Connect Sync

The following issues are known in Jamf Connect Sync:

  • [PI-007085] When an end user's Okta password is changed in the Okta Dashboard, Jamf Connect Sync may not prompt the end user to re-sync their new Okta password with their local password.
    Workaround: Quit Jamf Connect Sync, and then open and sign in to the app again.

  • [PI-007088] When "Automatically push last MultiFactor" is enabled and an end user's password is changed in the Okta Dashboard, signing in to Jamf Connect Sync with the new password may cause the the MFA push to stall.

  • [PI-007242] Jamf Connect Sync fails to display security question MFA prompts to users.

  • [PI-007521] When the KerberosRenew and TicketsOnSignIn preference keys are both set to true, Jamf Connect Sync does not obtain Kerberos tickets on sign-in.

Jamf Connect Verify

The following issues are known in Jamf Connect Verify:

  • [PI-007220] When Kerberos authentication is enabled, Kerberos tickets are not automatically obtained on initial log in, if a keychain item for Jamf Connect Verify does not exist.

  • Workaround: After signing in, click Kerberos Tickets in the Jamf Connect Verify menubar. If using Jamf Connect Login to provision users, set the CreateVerifyPasswords preference key to true, which will create a keychain item for Jamf Connect Verify.

  • [PI-007284] When file shares are configured with Jamf Connect Verify and Time Machine backups are configured and stored on a Time Capsule, Jamf Connect Verify will crash when Time Machine runs.

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