Today we released Jamf Connect 2.8.0 for general availability; this release includes the below details.
Key Feature Content
Passthrough Authentication for OneLogin and PingFederate: Organizations that use OneLogin and PingFederate with the Jamf Connect login window can now securely send the password entered by users in the sign-in web view to Jamf Connect for local authentication.
Jamf Connect Configuration Upload Integration with Jamf Pro: You can now upload configurations created in the Jamf Connect Configuration app directly to your organization's Jamf Pro instance. This eliminates the need to save the configuration profile locally and then manually upload the profile to Jamf Pro.
Set Jamf Connect as a Login Item: You can now set the Jamf Connect menu bar app as a macOS login item for users. This ensures that Jamf Connect automatically opens after login rather than needing to manually direct users to open the app from the /Applications folder.
Resolved Issues
- [PI-010318] Executing authchanger -reset -JamfConnect via Jamf Pro policy no longer returns a false positive "Failed to write file `default.profraw`" error message.
- [PI-010364] Custom icons used in the Sign In window are no longer stretched to fit the maximum allowed size (450 x 450 px).
Product Documentation
For more information, including Release Notes, please see the Jamf Connect Administrator Guide.
Thank you!
The Jamf Connect team
