The Allow unlocking toggle in Jamf Unlock is now enabled by default after users pair with their Mac so that users no longer need to manually turn on the Allow unlocking toggle after pairing. Let’s take a look back at Apple Configurator 1.0. Okta domain variants (e.g., oktapreview or okta-emea) are now recognized by Jamf Unlock, and no longer result in an error when configuring the app in Jamf Pro. It wasn’t that long ago that the process was much more complicated than it is today. Users are unable to leverage Safari user sessions by default unless their administrator sets the new preference to true. Jamf Unlock will no longer display the Jamf Unlock would like to use idp.com to sign in permission prompt when a user selects the Get started button unless their administrator sets the new preference to true.
This avoids users getting stuck on the pairing screen if their network connection is interrupted.Ī new preference key, Use Persistent Session ( key -use-persistent-session), enables admin control over Jamf Unlock's access to persistent Safari data, such as authentication settings.
#APPLE CONFIGURATOR JAMF CODE#
The QR code pairing times out after 30 seconds of inactivity. Pairing is faster between users' iOS or iPadOS devices and Macs. Support for scrolling, smaller device sizes, dynamic fonts, and messaging, including messages about unlocking successes and errors
Greeting users based on the time of day in their timezone, (e.g., "Good morning, David Engles")ĭisplaying the user's profile image, email address, name, and job title
0 kommentar(er)
