Release History

This page explains the release history of each Jamf Connect release, which includes the app specific versions in each Jamf Connect release.

Jamf Connect 1.18.1 (2020-03-12)

App

Version

Changes

Jamf Connect Configuration

1.8.2

Bug Fix

[PI-007810] Fixed an issue that prevented all required settings for configuring Jamf Connect with Google ID to display after choosing "GoogleID" from the Identity Provider pop-up menu.

Jamf Connect Login

1.11.1

Bug Fixes

  • [PI-007982] Fixed an issue that prevented account migration with Okta accounts from succeeding when the OIDCShortName preference key was used.

  • [PI-007363] Fixed an issue that prevented users from using local authentication via the Local Fallback setting when connected to a network without an internet connection.

  • [PI-007840] Fixed an issue that caused the Use Local Authentication by Default setting to be excluded from Jamf Pro's Application & Custom Settings payload options for configuring Jamf Connect.

Jamf Connect Sync

1.4.1

Bug Fixes and Enhancements

  • Jamf Connect Sync now logs users in to Okta with their default browser.

  • Fixed some UI issues that appeared when non-English languages were used with Jamf Connect Configuration

Jamf Connect Verify

1.5.1

Bug Fix

Fixed some UI issues that appeared when non-English languages were used with Jamf Connect Configuration

Jamf Connect 1.18.0 (2020-02-27)

App

Version

Changes

Jamf Connect Configuration

1.8.1

Bug Fixes

  • Fixed an issue that prevented users from resizing the Jamf Connect Configuration sidebar.

  • Fixed an issue that caused Jamf Connect Configuration to incorrectly export the OIDCScopes preference key.

Jamf Connect Login

1.11.0

UI Localization

The Jamf Connect Login UI now supports the following languages, if selected by users via System Preferences:

  • French

  • German

  • Japanese

  • Spanish

Jamf Connect Sync

1.4.0

UI Localization

The Jamf Connect Sync UI now supports the following languages, if selected by users via System Preferences:

  • French

  • German

  • Japanese

  • Spanish

Bug Fixes

  • [PI-007719] Fixed an issue that caused Jamf Connect Sync to unexpectedly check in with Okta when connected to a network without an internet connection, and then delete its keychain item after the check in failed.

  • Fixed an issue that caused text in one-time password (OTP) fields to not be treated as secure fields.

Jamf Connect Verify

1.5.0

UI Localization

The Jamf Connect Verify UI now supports the following languages, if selected by users via System Preferences:

  • French

  • German

  • Japanese

  • Spanish

Jamf Connect 1.17.0 (2020-02-13)

App

Version

Changes

Jamf Connect Configuration

1.8.0

Accessibility Support

Jamf Connect Configuration now supports Apple's native accessibility controls on the Mac.

Bug Fixes

  • JC-1079 Fixed an issue that caused the ROPG Provider setting, when configured, to be included and exported in all configurations.

  • JC-977 Fixed an issue that caused the DenyLocalExcluded preference key to incorrectly display in the Jamf Connect Configuration UI when imported from an configuration profile.

Jamf Connect Login

1.10.0

New Authentication and Authorization Settings

The following new settings can be used to further define user attributes used by Jamf Connect's authentication and authorization process. For more information about these settings, see Configuring Jamf Connect Login.

  • The OIDCShortName preference key specifies which attribute from an Okta ID token is used as the account short name. The short name is added as an alias to the user's local account.

  • The OIDCIDTokenPath and OIDCTokenPathRaw preference keys can store a user's formatted or raw ID token at a specified file path.

  • The OIDCScopes preference key can define custom scopes, which return additional claims in a user's ID token during authorization. Standard scopes include openid, profile, and offline_access. This key should be configured as a string with space-separated values.

Bug Fixes and Other Enhancements

  • [PI-007771] Fixed an issue that caused local passwords to sync with an Okta account's temporary password rather than a permanent password during account migration.

  • Fixed an issue that caused computers configured to use the pluggable authentication module (PAM) for sudo operations to enter an unstable state when users clicked Cancel in the authentication window.

  • Updated the text in the Jamf Connect login window to improve the login user experience.

Jamf Connect Sync

1.3.0

Microsoft Edge Added to Preferred Browser Options

Jamf Connect Sync now supports Microsoft Edge as a preferred browser choice for users. To select Microsoft Edge as the preferred browser, users can click Sign in in the Jamf Connect Sync menu bar application, and then select Microsoft Edge from the Browser drop down menu.

Bug Fixes

  • Fixed an issue that caused Jamf Connect Sync to stall on the sign in window when a Multifactor Authentication push fails.

  • Fixed an issue that caused Jamf Connect Sync to incorrectly prompt for a verification code when attempting to authenticate with a Yubikey.

Jamf Connect Verify

1.4.1

Bug Fixes

  • [PI-007694] Fixed an issue that caused Jamf Connect Verify to sometimes fail to update the login keychain password.

  • [PI-007706] Fixed an issue that caused Jamf Connect Verify to be unable to auto mount more than one file share at a time.

Jamf Connect 1.16.0 (2020-01-30)

App

Version

Changes

Jamf Connect Configuration

1.7.0

Configuration Storage

You can now save and edit configurations within the Jamf Connect Configuration app. Saved configurations are displayed in a sidebar on the left side of the window.

Jamf Connect Login

1.9.0

Enhancements

For target computers running macOS 10.13.x, you can now configure the opacity of the background image alpha channel with the BackgroundImageAlpha preference key. For more information, see Configuring Jamf Connect Login.

Jamf Connect Sync

1.2.2

Bug Fixes

  • [PI-007242] Fixed an issue that caused Jamf Connect Sync to fail to display security question MFA prompts to users.

  • [PI-007772] Fixed an issue that caused Jamf Connect Sync to display an incorrect message to users with a one-time password (OTP) as their only multifactor authentication (MFA) method.

  • [PI-007808] Fixed an issue that caused Jamf Connect Sync to blank out the password field of the login window when attempting to complete SMS multifactor authentication, preventing successful login.

Jamf Connect Verify

1.4.0

N/A

Jamf Connect 1.15.0 (2020-01-09)

App

Version

Changes

Jamf Connect Configuration

1.6.1

Bug Fixes

  • [PI-007757] Fixed an issue that caused the MigrateUsersHide preference key-value pair to appear as a string rather than an array of strings when exported into a configuration profile.

  • Fixed an issue that sometimes caused PLIST files to be signed unintentionally.

Jamf Connect Login

1.8.1

Bug Fixes

  • [PI-006872] Fixed an issue that caused the login window to be off-center on external monitors.

  • [PI-007796] Fixed an issue that caused local user account names to be created as "Lastname Firstname" rather than "Firstname Lastname" when Jamf Pro's Enrollment Customization settings were used to pass account information to Jamf Connect.

Jamf Connect Sync

1.2.1

Bug Fix

[PI-007436] Fixed an issue that sometimes caused Jamf Connect Sync to crash when multifactor authentication was configured to ask a security question.

Jamf Connect Verify

1.4.0

Support for Active Directory Short Names

You can now configure Jamf Connect Verify to prompt users for their Active Directory short name if it differs from their network username. The following preferences are now available in Jamf Connect Verify for this purpose:

  • KerberosShortNameAskMessage

  • KerberosShortName

  • KerberosShortNameAsk

For more information, see Configuring Jamf Connect Verify.

Jamf Connect 1.14.0 (2019-12-19)

App

Version

Changes

Jamf Connect Configuration

1.6.0

Bug Fixes and Other Enhancements

  • [PI-007449] Fixed an issue that, when creating a configuration for PingFederate, caused Jamf Connect Configuration to display the OIDC Tenant field as a required setting.

  • In the Login tab, the Local Fallback setting has been moved from the “Okta” section to the “User Creation” section.

Jamf Connect Login

1.8.0

Software Token Support for Multifactor Authentication

Jamf Connect Login now supports both hardware and software tokens, such as RSA SecurID software tokens, for multifactor authentication (MFA) with Okta.

Accessibility Support

Jamf Connect Login now supports Apple's native accessibility controls on the Mac.

Jamf Connect Sync

1.2.0

Accessibility Support

Jamf Connect Sync now supports Apple's native accessibility controls on the Mac.

Bug Fixes

  • [PI-007529] Fixed an issue that caused the Sign In window to display unwanted text in in the MFA pop-up menu options when using the MFARename preference key.

  • Fixed an issue that caused some multifactor authentication (MFA) prompts to unexpectedly close without an error message when an incorrect verification code was entered.

Jamf Connect Verify

1.3.0

Accessibility Support

Jamf Connect Sync now supports Apple's native accessibility controls on the Mac.

Jamf Connect 1.13.0 (2019-12-05)

Deprecation Notice: macOS 10.12 is no longer supported by Jamf Connect.

App

Version

Changes

Jamf Connect Configuration

1.5.0

Hybrid Identity Preferences for Azure AD

Jamf Connect Configuration now supports preferences used to configure Jamf Connect Login in Azure Hybrid Identity environments. The following preferences are now available in the Login tab:

  • ROPG Provider

  • ROPG Tenant

  • ROPG Discovery URL

  • ROPG Redirect URI

  • ROPG Client Secret

  • ROPG Success Codes

Resource Owner Password Grant (ROPG) Testing

You can now test your configuration to ensure that the ROPG authentication protocol, which Jamf Connect uses for password verification and synchronization, is correctly configured. To test ROPG authentication using Jamf Connect Configuration, navigate to Test > ROPG and enter your test user's username and password.

Bug Fix

Fixed an issue that prevented the setup assistant from displaying required settings for custom identity providers.

Jamf Connect Login

1.7.1

Bug Fixes and Enhancements

  • [PI-007469] Fixed an issue that prevented Jamf Connect Login from creating a keychain item for Jamf Connect Sync or Jamf Connect Verify for already existing local user accounts.

  • [PI-007551] Fixed an issue that caused the authchanger -reset command to place macOS loginwindow mechanisms in the incorrect order, which sometimes prevented FileVault password resets from succeeding.

  • [PI-007580] Fixed an issue that caused local user accounts created with Jamf Connect Login to use Bash rather than Zsh as the default shell on computers with with macOS 10.15 or later.

  • Fixed an issue that caused Jamf Connect Login to display an incorrect error message when Okta users entered an incorrect one-time password in a multi-factor authentication (MFA) prompt.

  • Fixed an issue that prevented the Help (?) Button from displaying any URL specified by the HelpURL preference key.

  • Fixed an issue that prevented the OIDCDefaultLocal preference key from being respected.

  • (Documentation Only) Added the OIDCDefaultLocal preference key to the Configuring Jamf Connect Login sections of this guide. When set to true, this key instructs Jamf Connect Login to use local authentication by default.

Jamf Connect Sync

1.1.0

Software Token Support for Multifactor Authentication

Jamf Connect Sync now supports both hardware and software tokens, such as RSA SecurID software tokens, for multifactor authentication (MFA).

Bug Fixes

  • [PI-007088] Fixed an issue that caused the Multifactor Authentication window to stall indefinitely during sign in when Automatically Push Last Multifactor was enabled.

  • [PI-007515] Fixed an issue that caused the Safari browser extension, when enabled, to redirect to Jamf Connect Sync for authentication when an Okta URL autofilled in the Safari search bar rather than after users pressed Return.

Jamf Connect Verify

1.2.1

Some existing references to NoMAD have been changed to Jamf Connect.

Jamf Connect 1.12.0 (2019-11-18)

Deprecation Notice: Support for macOS 10.12 will be discontinued in an upcoming release of Jamf Connect.

App

Version

Changes

Jamf Connect Configuration

1.4.0

Enhancements

  • You can now edit payload configuration profile data such as organization, payload name, payload identifier, payload description, and signing identity when saving configurations as .mobileconfig files.

  • You can now open .plist files with Jamf Connect Configuration

Jamf Connect Login

1.7.0

Enrollment Customization with Jamf Pro

If your environment uses the Enrollment Customization feature in Jamf Pro, Jamf Connect can receive user information when devices are enrolled with Jamf Pro. The Account Name (the username that was used to authenticate with your IdP) and the Account Full Name (the full name of the user) can be passed to Jamf Connect. After authenticating with their IdP, the user is presented with the Jamf Connect Login screen and must re-enter their password to continue with enrollment.

Notes:

  • Jamf Pro 10.17.0 or later is required to pass user information to Jamf Connect using an Enrollment Customization configuration.

  • To create local administrator accounts, you must use the CreateAdminUser preference key. User roles configured and stored in an ID token from your IdP will not be respected until a user's second log in.

For more information, see the Enrollment Customization Settings section in the Jamf Pro Administrator's Guide.

Bug Fix

[PI-007478] Fixed an issue that prevented the Jamf Connect login window from loading on start up, which displayed the following message: “Error: could not create request URL”.

Jamf Connect Sync

1.0.10

Bug Fixes

  • [PI-007396] Fixed an issue that prevented the MessageOTPEntry preference key from being respected when a one-time password (OTP) was the only multi-factor authentication (MFA) option enabled for Okta users.

  • [PI-007521] Fixed an issue that prevented Kerberos tickets from being obtained on sign-in when the KerberosRenew and TicketsOnSignIn preference keys were both set to true.

Jamf Connect Verify

1.2.0

Enhancement

Azure administrators can now use the ROPGSuccessCodes preference key with Jamf Connect Verify. This preference can specify error codes from Azure during an ROPG password verification, which should be interpreted as successful by Jamf Connect.

For possible error codes that may need to be configured in your environment, see the following documentation from Microsoft: https://docs.microsoft.com/azure/active-directory/develop/reference-aadsts-error-codes

Jamf Connect 1.11.0 (2019-11-07)

App

Version

Changes

Jamf Connect Configuration

1.3.1

Bug Fix

Fixed an issue that prevented Jamf Connect Configuration from including the Scopes and OIDCIgnoreCookies keys when saving .mobileconfig files for Jamf Connect Verify.

 

Jamf Connect Login

1.6.0

Enhancements

Jamf Connect Login now supports the LocalFallback key-value pair for all IdP's using OpenID Connect authentication. For more information, see Configuring Jamf Connect Login.

Bug Fixes

  • [PI-007513] Fixed an issue that caused a user's local account password to be removed or never created with Okta when SMS or a Yubikey was used as an MFA method.

  • [PI-007542] Fixed an issue that prevented Azure users with third-party conditional access polices from authenticating with Jamf Connect Login.

Jamf Connect Sync

1.0.9

Error Messaging Improvements

Some error messages have been improved to help users troubleshoot errors.

Jamf Connect Verify

1.1.6

Bug Fix

[PI-007542] Fixed an issue that prevented Azure users with third-party conditional access polices from authenticating with Jamf Connect Verify.

Jamf Connect 1.10.0 (2019-10-17)

App

Version

Changes

Jamf Connect Configuration

1.3.0

Enhancements

You can now save Jamf Connect configuration profiles in property list (.plist) file format. File format can be selected via the Setup Assistant or by navigating to File > Save after using advanced setup.

Jamf Connect Login

1.5.2

Bug Fixes

  • [PI-007465] Fixed an issue that, after using Google Cloud ID to create a local user account, prevented users from logging in after their first log out.

  • [PI-007220] Fixed an issue that, when Kerberos authentication was enabled, Kerberos tickets were not automatically obtained on initial log in if a keychain item for Jamf Connect Verify did not exist.

  • [PI-007254] Fixed an issue that, when integrated with Okta, caused logins to sometimes fail when user migration was enabled with a one-time password (OTP) MFA method.

  • [PI-007466] Fixed an issue that caused the Username and Password fields to be disabled when integrated with Okta and attempting to log in for the first time after setting up multi-factor authentication.

  • Fixed an issue that sometimes caused the login window for Okta users to become unresponsive while updating the local account password to match a recent Okta password change.

Jamf Connect Sync

1.0.8

N/A

Jamf Connect Verify

1.1.5

N/A

Jamf Connect 1.9.0 (2019-10-03)

App

Version

Changes

Jamf Connect Configuration

1.2.0

Enhancements

Additional Support for Jamf Connect Login Settings

The following Jamf Connect Login settings are now supported in Jamf Connect Configuration:

User Creation Settings:

  • KeychainCreates a keychain item for Jamf Connect Verify

  • Ignore RolesPrevents local accounts from being created or changed based on role assignments in your IdP

Appearance Settings:

  • Local Auth ButtonCustom text for the Local Auth button

  • Hide RestartHides the restart button

  • Hide ShutdownHides the shut down button

Script Settings:

  • Script PathSpecifies the path to a script or other executable. Only one script can be used at any time.

  • Script ArgumentsThe arguments used with a specified script

Okta Settings:

  • MFA MessageText displayed when a user must enter a one-time password (OTP) as a multi-factor authentication (MFA) method

  • KeychainCreates a keychain item for Jamf Connect Sync

Application Window Sizing

You can now re-size the Jamf Connect Configuration application window.

Bug Fix

Fixed an issue that caused some settings to be omitted from configuration profiles saved for Jamf Connect Verify.

Jamf Connect Login

1.5.1

Bug Fix

[PI-007444] Fixed an issue that prevented Okta users with a username in short name format (without an "@" symbol) from creating a local user account with Jamf Connect Login.

Jamf Connect Sync

1.0.8

Bug Fix

[PI-007282] Fixed an issue that prevented Okta users with SMS multi-factor authentication enabled from receiving a verification code correctly.

Jamf Connect Verify

1.1.5

Bug Fixes

  • [PI-007170] Fixed an issue that sometimes prevented changes to Preference Menu items from being saved.

  • Fixed an issue that caused Jamf Connect Verify to display an incorrect password error when the network connection is lost.

Jamf Connect 1.8.0 (2019-09-19)

App

Version

Changes

Jamf Connect Configuration

1.1.0

Enhancements

MFA Testing for Okta

You can now use the Okta Test window to test multi-factor authentication (MFA), if enabled in the Okta dashboard. When enabled, the Okta Test window will prompt you to select from Okta-enabled MFA options, and then complete the MFA prompt from the Okta Test window.

To learn more about using MFA with Okta, see the following Okta documentation: https://help.okta.com/en/prod/Content/Topics/Security/MFA.htm

Bug Fix

Fixed an issue that caused Jamf Connect Configuration to quit unexpectedly when the Reset button was pressed repeatedly.

Jamf Connect Login

1.5.0

Enhancements

Azure AD Hybrid Identity Support

Jamf Connect now supports authentication with environments that use both Azure AD and on-premise Active Directory (hybrid identity). Jamf Connect can be configured to authenticate users with Azure AD, and then sync a local account password with their on-premise AD password. Jamf Connect can be configured to support the following Azure AD authentication methods:

  • Password hash synchronization

  • Pass-through authentication

  • Federated integration (AD FS)

For more information about configuring Jamf Connect with an Azure AD hybrid identity solution, see the following Knowledge Base articles:

User Prompting Improvements

Users are now prompted to log in with their network account, if they attempt to log in locally but are not allowed because the DenyLocal key is set true and the user is not specified in the DenyLocalExcluded key.

Bug Fixes

  • [PI-007051] Fixed an issue that prevented the keychain item for Jamf Connect Login from being updated after an Okta password change.

  • [PI-007355] Fixed an issue that caused new local accounts based on an Azure AD username formatted as "first.last@example.com" to create the local account username as "First FirstLast".

Jamf Connect Sync

1.0.7

Bug Fixes

The following UI changes were made to the Preferences menu:

  • Added placeholder text with example values

  • Changed some preference setting labels to match between Jamf Connect Sync and Jamf Connect Configuration's Sync pane

Jamf Connect Verify

1.1.4

N/A

Jamf Connect 1.7.0 (2019-09-05)

App

Version

Changes

Jamf Connect Configuration

1.0.0

New Application

Jamf Connect Configuration is a new app that allows administrators to automatically configure and create computer configuration profiles for Jamf Connect apps. You can use Jamf Connect Configuration to do the following:

  • Select and specify Jamf Connect preferences.

  • Test configurations.

  • Save configuration profiles, which you can install locally or upload for deployment with an MDM solution.

  • Open an existing Jamf Connect configuration profile.

Note: You can also enable app analytics via Jamf Connect Configuration Preferences.

Jamf Connect Configuration is included in the Jamf Connect DMG and available for download in My Assets on Jamf Nation. For additional information, see Jamf Connect Configuration.

Jamf Connect Login

1.4.0

Enhancements

You can now enable users to configure a WiFi connection from the login window by adding the AllowNetworkSelection preference key to your Jamf Connect Login configuration profile. When set to true, AllowNetworkSelection displays the Network Connection button in the bottom-right corner of the login window. For more information, see Configuring Jamf Connect Login.

Jamf Connect Sync

1.0.6

N/A

Jamf Connect Verify

1.1.4

Bug Fixes

The following UI changes were made to the Preferences menu:

  • Added placeholder text with example values

  • Changed some preference setting labels to match between Jamf Connect Verify and Jamf Connect Configuration's Verify pane

Jamf Connect 1.6.2 (2019-08-22)

App

Version

Changes

Jamf Connect Login

1.3.3

Enhancements

You can use the OIDCIgnoreAdmin preference key to ignore user roles configured in your identity provider (IdP).

This key is best used if you are also using the CreateAdminUser preference key to create a local admin account, but do not want Jamf Connect Login to change the user's account status during the next log in.

Note: This feature fixes [PI-007186].

Bug Fixes

  • [PI-007186] Fixed an issue that sometimes caused already created local admin user accounts to become standard user accounts during the next log in, if user roles were also specified in your IdP.

  • [PI-007287] Fixed an issue that caused Azure passwords with ampersands (&) or plus signs (+) to prevent users from logging in.

Jamf Connect Sync

1.0.6

Bug Fix

[PI-006721] Fixed an issue that sometimes prevented users from changing their password via Kerberos with Jamf Connect Sync.

Jamf Connect Verify

1.1.3

Bug Fixes

  • [PI-007287] Fixed an issue that caused Azure passwords with ampersands (&) or plus signs (+) to prevent users from signing in.

  • [PI-007172] Fixed an issue that prevented Jamf Connect Verify's keychain item from being updated after a password change.

Jamf Connect 1.6.1 (2019-08-08)

App

Version

Changes

Jamf Connect Login

1.3.2

Bug Fix

[PI-007175] Fixed an issue that caused Jamf Connect Sync's keychain item to be inaccessible without user permission.

Jamf Connect Sync

1.0.5

N/A

Jamf Connect Verify

1.1.2

N/A

Jamf Connect 1.6.0 (2019-07-25)

App

Version

Changes

Jamf Connect Login

1.3.1

Enhancements

If using a one-time password (OTP) as a multi-factor authentication (MFA) method for Okta users, you can now use the MessageOTPEntry preference key to customize the text displayed to users when they are prompted for an OTP. For more information, see the Configuring Jamf Connect Login with Okta page in the Jamf Connect Login section of this guide.

Jamf Connect Sync

1.0.5

Bug Fix

[PI-007093] Fixed an issue that caused Jamf Connect Sync's keychain item to be erased when silent check occurred without a network connection.

Jamf Connect Verify

1.1.2

N/A

Jamf Connect 1.5.0 (2019-07-11)

App

Version

Changes

Jamf Connect Login

1.3.0

Enhancements

You can now set a local user account's UID to a custom value during account creation. This can be used to match a local user account's UID with their LDAP UID attribute. Local user account UIDs are customized with the UIDTool preference key, which specifies a path to an executable script that functions as a UID tool.

For additional information, see the UIDTool preference key description in the Configuring Jamf Connect Login section of this guide.

Bug Fix

[PI-007061] Fixed an issue that caused user migration to be skipped when the OIDCNewPassword preference key was set to true.

Jamf Connect Sync

1.0.4

N/A

Jamf Connect Verify

1.1.2

N/A

Jamf Connect 1.4.2 (2019-06-27)

App

Version

Changes

Jamf Connect Login

1.2.1

Bug Fixes

  • [PI-006590] Fixed an issue that caused Jamf Connect Login to omit suffixes or prefixes of a user's first or last name when creating a user's local username.

  • [PI-006866] Fixed an issue that caused Jamf Connect Login to create an unwanted Jamf Connect Verify keychain entry for Jamf Connect Sync users.

  • [PI-007019] Fixed an issue that prevented Jamf Connect Login from reading the OIDCAdmin preference key when integrated with OneLogin.

  • [PI-007034] Fixed an issue that prevented Okta users from logging in to a computer if they changed their Okta or local account password.

Jamf Connect Sync

1.0.4

N/A

Jamf Connect Verify

1.1.2

Bug Fix

[PI-006945] Fixed an issue that caused a race condition when automatically verifying a user's network and local passwords, which set the local password to an unknown value.

Jamf Connect 1.4.1

App

Version

Changes

Jamf Connect Login

1.2.0

(Documentation update only) Added documentation for enabling the Pluggable Authentication Module (PAM) that is installed with Jamf Connect Login.
For more information, see Pluggable Authentication Module (PAM).

Jamf Connect Sync

1.0.4

N/A

Jamf Connect Verify

1.1.1

Bug Fix

[JC-419] Fixed an issue that prevented PingFederate end users from obtaining Kerberos tickets when a domain was not specified in the user's short name.

Jamf Connect 1.4.0

App

Version

Changes

Jamf Connect Login

1.2.0

N/A

Jamf Connect Sync

1.0.4

N/A

Jamf Connect Verify

1.1.0

Enhancements

  • Added support for PingFederate as a cloud identity provider (IdP). To integrate Jamf Connect Verify with PingFederate, see Configuring Jamf Connect Verify.

  • Added support for custom IdPs. For more information, see Configuring Jamf Connect Verify

  • Added a launch agent that instructs macOS to launch Jamf Connect Verify on log in.

  • Added the following preference keys, which display a success message when a user successfully signs in:

    • AlwaysShowSuccess

    • MessagePasswordSuccess

Jamf Connect 1.3.0

App

Version

Changes

Jamf Connect Login

1.2.0

Enhancements

Added support for PingFederate as a cloud identity provider (IdP). To integrate Jamf Connect Login with PingFederate, see Integrating with PingFederate.

Bug Fixes

  • [JC-322] Fixed an issue that sometimes caused the login window for Microsoft Azure AD users to be be hidden when users clicked on the background.

  • [PI-006887] Fixed an issue that prevented Okta users from selecting multi-factor authentication (MFA) pop-up menu items.

Jamf Connect Sync

1.0.4

Bug Fixes

  • [PI-006902] Fixed an issue that sometimes prevented users from being prompted to sync their recently changed network password with their local password.

  • [JC-377] Fixed an issue that sometimes prevented Duo MFA prompts from closing automatically.

  • [JC-343] Fixed an issue that prevented password changes from updating in the user's keychain.

  • [JC-388] Status menu items no longer appear as selectable.

  • [JC-398] Jamf Connect Sync's keychain item is now deleted if the silent password check fails.

Jamf Connect Verify

1.0.2

N/A

Jamf Connect 1.2.3

App

Version

Changes

Jamf Connect Login

1.1.3

Enhancements

Added the LocalHelpFile preference key that specifies a path to a local file. Users can access the file by clicking the "Help" button in the Jamf Connect Login window.
For more information, see Configuring Jamf Connect Login.

Jamf Connect Sync

1.0.3

Deprecations

Preferences written to the " menu.nomad.NoMADPro" preference domain will no longer be respected. All Jamf Connect Sync preferences must be written exclusively to "com.jamf.connect.sync".

Bug Fix

Fixed an issue that prevented the Duo MFA window from resizing correctly when using a custom window title.

Jamf Connect Verify

1.0.2

Bug Fix

[PI-006880] Fixed an issue that unexpectedly required users to sign in with their shortname instead of their full network username.

Jamf Connect 1.2.2

App

Version

Changes

Jamf Connect Login

1.1.2

Enhancements

When Jamf Connect Login is integrated with Microsoft Azure AD, you must grant admin consent to the app in the Azure portal. For instructions, see the following documentation from Microsoft: https://docs.microsoft.com/azure/active-directory/manage-apps/configure-user-consent

Bug Fix

Fixed an issue that sometimes prevented Microsoft Azure AD users from using local authentication without a network connection.

Jamf Connect Sync

1.0.2

N/A

Jamf Connect Verify

1.0.1

N/A

Jamf Connect 1.2.1

App

Version

Changes

Jamf Connect Login

1.1.1

Bug Fix

Fixed an issue that caused the login window to display a blank user interface when Jamf Connect Login was integrated with Microsoft Azure AD.
Important: The login window user experience has changed for Microsoft Azure AD users. For more information, see Benutzererlebnis mit Jamf Connect Login.

Jamf Connect Sync

1.0.2

Bug Fix

Fixed an issue that prevented trial users from testing Jamf Connect Sync.

Jamf Connect Verify

1.0.1

Bug Fix

Fixed an issue that prevented trial users from testing Jamf Connect Verify.

Jamf Connect 1.2.0

App

Version

Changes

Jamf Connect Login

1.1.0

Enhancements

  • Added support for the following cloud identity providers (IdPs):

    • Google Identity
      Note: The OIDCNewPassword key must be set to "true" to successfully authenticate or create a new user on a computer.

    • IBM Cloud Identity

    • OneLogin

  • Added Jamf Connect branding to the default login window UI for Okta configuration.

Bug Fix

Fixed an issue that prevented users from successfully signing in with the Local Auth button on a user's first login attempt.

Jamf Connect Sync

1.0.1

Bug Fix

Fixed an issue that prevented the Google Chrome browser extension from redirecting from Okta to Jamf Connect Sync.

Jamf Connect Verify

1.0.0

N/A

Jamf Connect 1.1.1

App

Version

Changes

Jamf Connect Login

1.0.1

Enhancements

Logs are now written locally in the following location: /private/tmp/jamf_login.log.
For more information, see the Collecting Logs in Jamf Connect Login Knowledge Base article.
Note: This log file is deleted during each reboot of the computer.

Bug Fixes

  • Fixed an issue that required the OIDCProvider key to be specified when configuring the Okta loginwindow.

  • Fixed an issue that prevented existing users from updating their local passwords after their OpenID Connect network password changed.

Jamf Connect Sync

1.0.0

N/A

Jamf Connect Verify

1.0.0

N/A

Jamf Connect 1.1.0

App

Version

Changes

Jamf Connect Login

1.0.0

N/A

Jamf Connect Sync

1.0.0

Enhancements

  • Implemented Jamf Connect branding

  • Added the ability to mount files shares via a configuration profile

  • The GetCertificateAutomatically key now automatically gets a certificate from a Windows web CA on login

  • Added the following preference keys:

    • PasswordCheckUpdateTimeSpecifies an integer for local password synchronization

    • CenterSignIn–Ensures the sign in window is always centered on the user's screen

    • KeyChainItemsInternet–Determines which internet accounts Jamf Connect Sync should synchronize with the user's local account.

Jamf Connect Verify

1.0.0

N/A

Jamf Connect 1.0.0

App

Version

Changes

Jamf Connect Login

1.0.0

Enhancements

  • Added integration with Microsoft Azure AD

  • Added a macOS loginwindow plugin that uses the public authentication APIs

  • Added the PAM (Pluggable Authentication Module) module to allow for sudo authentication to Microsoft Azure AD

Jamf Connect Sync

N/A

N/A

Jamf Connect Verify

1.0.0

Enhancements

Added the ability to sync local user passwords with Microsoft Azure AD network passwords

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