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.

Jamf Connect Configuration

The following issue is known in Jamf Connect Configuration:

  • [PI-007892] When ope ning a Jamf Connect Login PLIST file with Jamf Connect Configuration, the OIDCAdmin preference key is excluded if it is configured as an array of strings.

  • [PI-008025] Configuration profiles created by Jamf Connect Configuration fail to upload to Jamf Now.
    Workaround: Before uploading to Jamf Now, open the configuration profile with a text editor and change the root-level PayloadType key-value pair from "com.jamf.connect.login" to "Configuration".

Jamf Connect Login

The following issues are known in Jamf Connect Login:

  • [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-007651] When Jamf Connect Login is configured with Okta and the DenyLocal and Migrate preference keys are set to true, DenyLocal is not enforced and users can log in with any local account credentials.

  • [PI-007964] The -postAuth flag for the authchanger binary orders the RunScript and Notify mechanisms incorrectly.

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-007628] When a user’s password is changed outside of the Jamf Connect Sync application, a password change prompt appears with the password autofilled instead of the username.

  • [PI-007973] When using the Application & Custom Settings payload in Jamf Pro to configure Jamf Connect Sync, the Update Keychain Items (KeychainItems) and Sync Password with Internet Keychain Items (KeychainItemsInternet) settings do not display a configurable field.

  • [PI-008001] When end users sign in with their Active Directory short name, the Sign In window does not close after sign-in completes.

Jamf Connect Verify

The following issues are known in 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.

  • [PI-007628] When a user’s password is changed outside of the Jamf Connect Verify application, a password change prompt appears with the password autofilled instead of the username.

  • [PI-007723] The Self Service menu bar item cannot open a custom file path that contains spaces.

  • [PI-007725] Jamf Connect Verify does not respect the MenuIconActive preference key.

  • [PI-007890] When signing in to Jamf Connect with Kerberos enabled, users are not prompted to sync their local and network passwords if they do not match.
    Workaround: Sign in to Jamf Connect Verify a second time.


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