FAQ's

What permissions are required for the api user?

Jamf Pro Server Objects

Privilege	Create	Read	Update	Delete
Computers	X	X

PI-008067 has been opened with Jamf Support regarding the need for the Create permission on Computers. It makes sense to have the Update permission on Computers as well as the Create permission for File Attachments, but this is currently not the case. If you are using this workflow, I ask that you please email support@jamf.com to build the number of cases attached to this and show the severity of the issue.

Troubleshooting

If you're having problems getting the script to work, please add the below printf statement just before the Cleanup section to help determine what issues you are having and validate what is being passed in the script. Please do not leave this in for production use and never share your username or password.

printf "\n\n===== Logging =====\nJamf Pro URL: %s\nJamf Pro User: %s\nJamf Pro Pass: %s\n\nSerial Number: %s\nCurrent User: %s\nHost Name: %s\nTime Stamp: %s\n\nOS Version: %s\nJamf Pro ID: %s\n\n\n" "$jamfProURL" "$jamfProUser" "$jamfProPass" "$mySerial" "$currentUser" "$compHostName" "$timeStamp" "$osMajor.$osMinor" "$jamfProID"

Base64 Encode/Decode

Although, not as secure as Encrypted Strings, there are still some times where you will want to use this option, such as where credentials need to be included in an Extension Attribute! Below are example on how to encode and decode credentials for use with base64.

Encode Credentials

josh.roskos@MarvinsDepressedMBP:~$ echo "jamf1234" | base64
amFtZjEyMzQK

Decode Credentials

josh.roskos@MarvinsDepressedMBP:~$ echo "amFtZjEyMzQK" | base64 -d
jamf1234

or

josh.roskos@MarvinsDepressedMBP:~$ jamfProPass="amFtZjEyMzQK"
josh.roskos@MarvinsDepressedMBP:~$ jamfProPass=$(echo "$jamfProPass" | base64 -d)
josh.roskos@MarvinsDepressedMBP:~$ echo $jamfProPass
jamf1234