Configuring the JamfAAD Check-in to recheck for a valid Microsoft Entra ID token

Technical Paper: Device Compliance with Microsoft Entra and Jamf Pro

Solution

Application

Content Type

Technical Documentation

Utilities & Services

ft:locale

en-US

To resolve issues with users in an unresponsive state or network issues, you can configure the JamfAAD to recheck for a valid Microsoft Entra ID token at check-in by using the tokenRetryCount and tokenRetryWaitTime preferences. By default, tokenRetryCount is set to zero retries and tokenRetryWaitTime is set to five seconds.

You can configure the JamfAAD check-in in the following ways:

Deploy a PLIST file using a configuration profile with the Custom Settings payload configured.
Run a script using a policy with the execution frequency of "Once per user per computer".

The following examples show how to configure the JamfAAD to retry three times with 42 seconds between each retry.

PLIST Example

To configure JamfAAD check-in by deploying a PLIST file, use the following example:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>tokenRetryCount</key>
	<integer>3</integer>
	<key>tokenRetryWaitTime</key>
	<integer>42</integer>
</dict>
</plist>

Script Example

To configure JamfAAD check-in by running a script using a policy with the execution frequency of "Once per user per computer", use the following example:

#!/bin/sh
defaults write com.jamf.management.jamfAAD tokenRetryWaitTime -float 42
defaults write com.jamf.management.jamfAAD tokenRetryCount -int 3

For more information on how to run a script, see Scripts in the Jamf Pro Documentation.