When scoping the policy, scope whatever users are out in the field supporting these devices, so this policy will show up when they sign into Self Service. Enable the policy for Self Service and title it whatever you’d like. Make sure to set the frequency to “ongoing” and do not set a trigger. Once this script is completed, upload it into Jamf and create a policy to run it. The API call we will be utilizing to list out the Jamf Pro user accounts is: jamfUserIDs=$( curl -s -X GET '$jssHost/JSSResource/accounts' -H 'accept: text/xml' -H 'Authorization: Bearer $ giving up after 10000Īnd of course, make sure to enter your exit code at the end: exit 0 I should note that my API scripts from here on out will be utilizing bearer token authentication, since this is going to be required going forward with Jamf Pro sometime in the fall. Also, if this is a process that needs to be run on any recurring basis, saving it in a script makes the process nice and easy to repeat. This way, I can write notes or whatever else I want in the spreadsheet and then submit it to the higher ups easily. I figured I could just go look in Jamf Pro, write down the names of the accounts and their access summary, but what fun is that? Instead, I wrote up a script that outputs a CSV of all of the user accounts and some of their attributes. I was recently asked by my security team to perform an audit and produce a report of user accounts present in Jamf Pro. Since my last post, I received my Jamf Pro 400 certification! Woohoo! I haven’t posted in a while due to being rather busy.

What is jamf recon