Today we released Jamf Connect 2.6.0 for general availability; this release includes the below details.
Key Feature Content
Passthrough Authentication for Microsoft Azure AD: Organizations that use Microsoft Azure AD with the Jamf Connect login window can now securely send the password entered by users in the Microsoft sign-in web view to Jamf Connect for local authentication. This allows Jamf Connect to complete network and local authentication without prompting users to re-enter a password. During local account creation, this ensures that the network password is automatically used as the local password.
Resolved Issues
- [PI-008964] Okta MFA challenges that expire due to user inactivity are now canceled in Jamf Connect and allow users to re-attempt authentication.
- [PI-009948] The menu bar app no longer attempts continuous Kerberos authentication attempts during networks checks when an account is locked out in Active Directory.
- [PI-010139] Custom Sign In window logos are now scaled to fit the window and are automatically limited to 450x450 pixels.
- [PI-010199] The Welcome to Jamf Connect window now correctly displays an image of the menu bar app icon.
- [JC-3045] Okta Verify number challenges now display as a sheet attached to the Sign In window rather than a separate window.
Product Documentation
For more information, including Release Notes, please see the Jamf Connect Administrator Guide.
Note: Jamf Unlock with the macOS Login Window and Jamf Connect password sync with Google ID will be including in our next beta test, coming soon! If you are interested in beta testing these exciting new features, please log into your Jamf Account and check Beta Forums to enroll once available.
Thank you!
The Jamf Connect team
