Just wondering if anyone is having any success using Jamf Connect with macOS Monterey?
Currently we are working through internal systems readiness with macOS Monterey beta testing, and when using Jamf Connect (v2.4.3) with Monterey many issues are being experienced.
At present experiencing the following issues:
Also to verify, testing has been carried out on both Intel & M1 Macs. The tests have also been conducted on Macs upgraded from Big Sur to Monterey in addition to carrying out clean installations of Monterey, with the same results being experienced.
More than anything just curious as to wether anyone is seeing success when using Jamf Connect via Okta for authentication on Macs running Monterey.
Solved! Go to Solution.
Not that 2.4.4 also has a regression in it.
Connect 2.4.4 introduced PI-010087, a regression, for organizations with more than one of the following managed preferences in their configuration: OIDCAccessClientID, OIDCAdminClientID, OIDCSecondaryAccessClientID
Issue description: When signing in, only the first of the available client IDs is used for evaluating user access and permissions. As an example, configurations with both OIDCAccessClientID and OIDCAdminClientID can result in a user logging in to their local account and being demoted from administrator privileges to a standard user account. Configurations with none or only one of these preferences enabled should not be affected. As a workaround, modify the configuration to remove additional client IDs that should not be evaluated.
Connect 2.4.4 has been removed from auto-deployment settings for Jamf Pro customers - Connect 2.4.3 will be displayed as the most current version available until a solution can be made available via a future update.
Connect 2.4.4 will remain available for download from Jamf Account.