Using Jamf Connect with macOS Monterey - Beta Testing

[dan_ashley]

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:

• If using the "tab" key to switch between username & password boxes the mac will lock up and requires to be powered off.
• When using Okta for SSO, Jamf Connect will not login using just a username, instead it requires a users full email address to be entered in to the username field.
• Authentication through Jamf Connect seems to always fail on 1st attempt but is then successful on subsequent login attempt.
• 1st login attempt is only successful if network connectivity is disabled so that cached credentials are used.
• On M1 Macs, although Jamf Connect will authenticate successfully using Okta, before macOS desktop loads user is immediately logged back out unless network connectivity is disabled so that cached credentials are used for login.

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.

[Pickyvegan]

I'd start with turning off IP masking, I've seen some trouble caused by it in other apps and setups. It's in iCloud settings.

[DBrowning]

I'd suggest testing Monterey Beta 6 with JC 2.4.4 for the "tab" key issue.

[dan_ashley · Accepted solution]

Have found that Jamf Connect v2.4.4 fixes all the identified issues with macOS Monterey when running Monterey beta 5 or 6.

Thanks Jamf for the new version of Jamf Connect 🙂

[Geissbuhler]

This also resolved for us

[_andrea]

Hi,

On Jamf Connect 2.4.5 looks like i still have this one issue you mentioned

• When using Okta for SSO, Jamf Connect will not login using just a username, instead it requires a users full email address to be entered in to the username field.

Did you test it out yet?

[MatG]

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.