Skip to main content

Today we released Jamf Connect 2.2.0 for general availability; this release includes the below details.

Support for OneLogin OpenID Connect Version 2 Service: Jamf Connect now supports the version 2 endpoints of OneLogin's OpenID Connect service.
• Important: OneLogin will deprecate version 1 of their OpenID Connect service on January 26. To ensure OneLogin authentication continues to succeed with Jamf Connect, you must do the following:
• Update your Jamf Connect configuration profiles to include a tenant ID
• Upgrade to Jamf Connect 2.2.0
For additional information about OneLogin's OpenID Connect service migration, see the Upgrade v1 to v2 developer documentation from OneLogin.
For instructions on updating your Jamf Connect configuration profiles, see the Migrating to OneLogin's Version 2 OpenID Connect Service with Jamf Connect Knowledge Base article.

Bomgar Bug Fix: [PI-009069] Fixed an issue that caused the Jamf Connect login window to disappear after 10 to 30 seconds of inactivity when Bomgar or another application was configured to run on startup.

Product Documentation
For more information, including Release Notes, please see the Jamf Connect Administrator Guide.

Thank you!
The Jamf Connect team

Has demobilize been tested on M1 Mac's?
I've been trying demobilize using NoMAD 1.4 and it produces some odd results, like double logins.

Shit, PI-009104 is still not fixed :-/

Seems that Jamf Connect and NoMAD Login demobilize end up making the accounts on M1's have double login.

@Flaurian we are also waiting for PI-009104 to be resolved. Until that we can't use JC2 at all because we can't ensure that the password meets the requirements, so we are stuck with JC 1.19.3 :-(

What does MatG mean by demobilize?

@Leo_JAMF_PRO Demobilize means change a mobile account to a standard account at login. A lot of folks are doing if they are not binding their Macs to Microsoft Active Directory.

Terms & ConditionsCookie settingsAccessibility statement