├── README.md
├── download-extension-attributes.sh
└── update-extension-attributes.sh


/README.md:
--------------------------------------------------------------------------------
 1 | Casper Suite - Update Extension Attributes
 2 | =========================
 3 | 
 4 | ## Description
 5 | This set of scripts was designed to work with the Casper Suite for Mac management.
 6 | The purpose of the scripts is to allow a Mac Casper Suite administrator to update any number of Extension Attribute values on their managed Macs, on as frequent a basis as they want, without needing to perform a full inventory collection.
 7 | 
 8 | ## Compatibility
 9 | - The **update-extension-attributes.sh** bash script will work in the Casper Suite 8 and 9 series.
10 | - The companion **download-extension-attributes.sh** bash script will only work in the Casper Suite 9 series.
11 | 
12 | ## Requirements and Workflow
13 | The requirements to enable this functionality is as follows
14 | - A JSS API account with both **read** and **write** privileges to your JSS
15 | - A copy of any or all Extension Attributes scripts that can be distributed to your clients<br>
16 | Note: Each Extension Attribute script must contain a line indicating the EA Display Name as it appears in the JSS (see [**Setting up your EA scripts**](https://github.com/mm2270/UpdateExtensionAttributes#setting-up-your-ea-scripts) below for details)
17 | 
18 | ### General Workflow:
19 | - A directory is distributed to your Mac clients containing any number of Extension Attribute scripts
20 | - The **update-extension-attributes.sh** script is run on Macs that contain this directory, typically using a Casper Suite policy
21 | - The script will cycle through all scripts in the given directory, capturing their results
22 | - Each result is placed into a final xml file that is then uploaded to the Mac's JSS record using the Casper Suite API PUT function
23 | 
24 | Note that the Extension Attribute scripts directory can be protected by making it hidden and/or protected by having it owned by the root account, as long as the "update" script is running with root privileges.
25 | 
26 | ### Setting up your EA scripts:
27 | In order for the script to properly set up the final xml file for upload, it needs to know the correct EA Display Name for each script as it encounters it.
28 | To do this, you will need to edit each script to contain a single commented out line in the following format:
29 | ```
30 | #ea_display_name	Actual Display Name
31 | ```
32 | 
33 | The whitespace between **#ea_display_name** and **Actual Display Name** is a single tab character. This is important. A space will not be recognized correctly. This line can be anywhere in the script. The **update-extension-attributes** script will look for the line and pull the EA Display Name to use for the xml file. The readable display name can contain spaces and most special characters, such as dashes, colons, etc. (see the Known Issues section for more)
34 | 
35 | In general, this should be the only necessary change to your Extension Attribute scripts. However there are some known issues in relation to the results the scripts may output. See the [**Known Issues**](https://github.com/mm2270/UpdateExtensionAttributes#known-issues) section below for more information.
36 | 
37 | ### Using the **download-extension-attributes** companion script:
38 | The **download-extension-attributes.sh** script is a companion script that can be used in conjunction with a Casper Suite 9 series JSS to pull down all Extension Attributes into discrete script files to a given directory. The script will also verify each script by running them against the Mac and checking both the output and exit status. Any scripts that fail will be moved to a sub directory. Any scripts that contain illegal characters in the output will be moved into a separate sub directory.
39 | 
40 | For usage information, run the scrpt on the command line as follows:
41 | ```
42 | /path/to/script/download-extension-attributes.sh -h
43 | ```
44 | 
45 | ## Known Issues
46 | The following are the current known issues with these scripts
47 | 
48 | **Illegal characters**<br>
49 | There are several illegal characters that, while they may work without errors in your regular Extension Attribute scripts, can cause a failure of the resulting xml file when the upload is attempted.
50 | Here are the currently known characters:
51 | -   ```< & >```    *(Less than, Greater than)*   When used in the format of ```<some data>```, will cause the xml upload to fail as it sees these as xml tags and believes the xml file to be malformed
52 | -   ```%```    *(Percent symbol)*   Cannot be used in the result. Causes the upload to fail with an error
53 | -   ```,```    *(Comma)*   Cannot be used in the result. Causes the upload to fail with an error
54 | -   ```*```    *(Asterisk)*   Cannot be used in the result. Causes the upload to fail with an error
55 | 
56 | The **download-extension-attributes** script will make a best effort to identify scripts that contain any of the above characters in the results and move these scripts into a **Problem_scripts** sub directory.<br>
57 | Any problem or failed scripts will remain in these directories, so you'll have an opportunity to examine them and rectify any issues if desired. Once confirmed working, you'll need to move the scripts into the top level of the scripts directory. The **update-extension-attributes** script only searches one level deep for script files to run at execution time.
58 | 
59 | **Multi line results display**<br>
60 | Depending on the specific version of the JSS you're using, multi line Extension Attribute results may not appear properly when viewed in the JSS.<br>
61 | This often turns out to be a bug in the JSS version and not necessarily an issue with the script. Early versions of Casper Suite 9.x had this issue, but has been resolved in at least version 9.3, but possibly earlier releases.
62 | 


--------------------------------------------------------------------------------
/download-extension-attributes.sh:
--------------------------------------------------------------------------------
  1 | #!/bin/bash
  2 | 
  3 | ## Script name:		download-extension-attributes.sh
  4 | ## Author:		Mike Morales (@mm2270 on JAMFNation)
  5 | ##			https://jamfnation.jamfsoftware.com/viewProfile.html?userID=1927
  6 | ## Last change:		2014-05-14
  7 | 
  8 | ## Description:		Script to download all Extension Attribute scripts from a
  9 | ##			Casper Suite version 9.x JSS. For more detailed information,
 10 | ##			run the script in Terminal with the -h flag
 11 | 
 12 | ## The following section contains the only variables that should be manually edited in
 13 | ## the script. They can also be assigned to the script as Casper Suite parameters.
 14 | ## Read the descriptions for more info.
 15 | 
 16 | ## If you choose to hardcode API information into the script, set the API Username and
 17 | ## API Password here. Note: The API account only needs 'read' privileges to pull
 18 | ## Extension Attribute scripts
 19 | 
 20 | apiUser=""		## Set the API Username here if you want it hardcoded
 21 | apiPass=""		## Set the API Password here if you want it hardcoded
 22 | jssURL=""		## Set the JSS URL here if you want it hardcoded
 23 | 
 24 | ## Set the script downloads folder path here.
 25 | ## Default path is within the JAMF directory in "extension_attributes"
 26 | scriptDownloadDir="/Library/Application Support/JAMF/extension_attributes"
 27 | 
 28 | ################################ DO NOT EDIT BELOW THIS LINE ################################
 29 | 
 30 | script=$(basename $0)
 31 | directory="$( cd "$( dirname "$0" )" && pwd )"
 32 | 
 33 | ## Help / Usage function
 34 | usage ()
 35 | {
 36 | cat << EOF
 37 | SYNOPSIS
 38 | 	sudo script.sh -a "api_user" -p "api_password" -s "server"
 39 | 	or
 40 | 	sudo jamf runScript -script "script.sh" -path "/path/to/" -p1 "api_user" -p2 "api_password" -p3 "server"
 41 | 
 42 | COMPATIBILITY:
 43 | 	Casper Suite version 9.x
 44 | 	
 45 | OPTIONS:
 46 | 	-h	Show this usage screen
 47 | 	-a	API account username
 48 | 	-p	API account password
 49 | 	-s	JSS Server address [optional]
 50 | 
 51 | DESCRIPTION:
 52 | 	This script can be used to download a copy of all Extension Attribute scripts
 53 | 	located on the Casper Suite server specified in the server option.
 54 | 	The Casper Suite server URL is optional. If not specified at run time, the script
 55 | 	will attempt to obtain the JSS address from the client's settings.
 56 | 	
 57 | 	The script can be run in two primary ways.
 58 | 	1. Calling the script directly on the shell
 59 | 	
 60 | 	Example:
 61 | 	sudo "$0" -a "api_username" -p "api_password" -s "https://jss.server.com:8443"
 62 | 	
 63 | 	2. Using the jamf binary
 64 | 	
 65 | 	Example:
 66 | 	sudo jamf runScript -script "$script" -path "$directory" -p1 "api_username" -p2 "api_password" -p3 "https://jss.server.com:8443"
 67 | 	
 68 | 	You may also use the script directly in a JSS policy, specifying the API username,
 69 | 	API password and (optionally) the JSS URL in parameters 4 through 6, respectively.
 70 | 
 71 | NOTES:
 72 | 	It is recommended to enclose the API username, API password and JSS URL in double quotes
 73 | 	to protect the script against any special characters or spaces in the strings.
 74 | 		
 75 | EOF
 76 | exit
 77 | }
 78 | 
 79 | ## Run loop to check for passed args on the command line
 80 | while getopts ha:p:s option; do
 81 | 	case "${option}" in
 82 | 		a) apiUser=${OPTARG};;
 83 | 		p) apiPass=${OPTARG};;
 84 | 		s) jssURL=${OPTARG};;
 85 | 		h) usage;;
 86 | 	esac
 87 | done
 88 | 
 89 | ## Check to see if the script was passed any script parameters from Casper
 90 | if [[ "$apiUser" == "" ]] && [[ "$4" != "" ]]; then
 91 | 	apiUser="$4"
 92 | fi
 93 | 
 94 | if [[ "$apiPass" == "" ]] && [[ "$5" != "" ]]; then
 95 | 	apiPass="$5"
 96 | fi
 97 | 
 98 | if [[ "$jssURL" == "" ]] && [[ "$6" != "" ]]; then
 99 | 	jssURL="$6"
100 | fi
101 | 
102 | ## Finally, make sure we got at least an apiUser & apiPass variable, else we exit
103 | if [[ -z "$apiUser" ]] || [[ -z "$apiPass" ]]; then
104 | 	echo "API Username = $apiUser\nAPI Password = $apiPass"
105 | 	echo "One of the required variables was not passed to the script. Exiting..."
106 | 	exit 1
107 | fi
108 | 
109 | ## If no server address was passed to the script, get it from the Mac's com.jamfsoftware.jamf.plist
110 | if [[ -z "$jssURL" ]]; then
111 | 	jssURL=$( /usr/bin/defaults read /Library/Preferences/com.jamfsoftware.jamf.plist jss_url 2> /dev/null | sed 's/\/$//' )
112 | 	if [[ -z "$jssURL" ]]; then
113 | 		echo "JSS URL = $jssURL"
114 | 		echo "Oops! We couldn't get the JSS URL from this Mac, and none was passed to the script"
115 | 		exit 1
116 | 	else
117 | 		echo "JSS URL = $jssURL"
118 | 	fi
119 | else
120 | 	## Make sure to remove any trailing / in the passed parameter for the JSS URL
121 | 	jssURL=$( echo "$jssURL" | sed 's/\/$//' )
122 | fi
123 | 
124 | ## Set up the JSS Extension Attribute URL
125 | jssEAURL="${jssURL}/JSSResource/computerextensionattributes"
126 | 
127 | ## Run quick check on access to the JSS API
128 | curl -skfu "${apiUser}:${apiPass}" "${jssEAURL}" 2>&1 > /dev/null
129 | 
130 | if [[ "$?" != "0" ]]; then
131 | 	echo "There was an error retrieving information from the JSS.
132 | Please check your API credentials and/or the JSS URL, and ensure the JSS is accessible from your location. Exiting now..."
133 | 	exit 1
134 | fi
135 | 
136 | ## Create the extension_attributes directory if not present
137 | if [[ ! -d "$scriptDownloadDir" ]]; then
138 | 	mkdir "$scriptDownloadDir"
139 | fi
140 | 
141 | ## Begin Extension Attribute script download process
142 | echo "Step 1:	Gathering all Extension Attribute IDs from the JSS..."
143 | ## Generate a list of all Extension Attribute IDs we can pull from the JSS using the API
144 | allExtAttrIDs=$( curl -skfu "${apiUser}:${apiPass}" "${jssEAURL}" | xpath /computer_extension_attributes/computer_extension_attribute/id[1] 2>&1 | sed -e 's/<id>//;s/<\/id>//;s/-- NODE --//' | sed -e '/Found/d;/^$/d' | sort -n )
145 | 
146 | ## Now read through each ID gathered and get specific information on each EA from the JSS
147 | echo "Step 2:	Pulling down each Extension Attribute from the JSS..."
148 | 
149 | downloadCount=0
150 | while read ID; do
151 | 	## Get the EA name from its JSS ID
152 | 	ea_Name=$( curl -sku "${apiUser}:${apiPass}" "${jssEAURL}/id/${ID}" | xpath /computer_extension_attribute/name[1] 2>&1 | sed -e 's/<name>//;s/<\/name>//;s/-- NODE --//' | sed -e '/Found/d;/^$/d' )
153 | 	## Get the actual script contents from the API record for the EA
154 | 	ea_Script=$( curl -sku "${apiUser}:${apiPass}" "${jssEAURL}/id/${ID}" | xpath /computer_extension_attribute/input_type/script[1] 2>&1 | sed -e 's/<script>//;s/<\/script>//;s/-- NODE --//;s/:/\\:/' | sed -e '/Found/d;/^$/d' )
155 | 	## Get the first line, which should be a shebang of some kind
156 | 	firstLine=$( echo "${ea_Script}" | head -1 )
157 | 	## If it looks like the first line begins with a shebang...
158 | 	if [[ $( echo "$firstLine" | grep "^#\!" ) ]]; then
159 | 		## ...grab the script's interpreter
160 | 		shellEnv=$( echo "$firstLine" | awk -F'/' '{print $NF}' | perl -pi -e 'tr/\cM//d;')
161 | 		## If the script's interpreter ends in sh (.sh, .bash, .ksh, csh, etc)...
162 | 		if [[ "$shellEnv" =~ sh$ ]]; then
163 | 			## ...set the script extension to .sh
164 | 			scriptExt="sh"
165 | 		else
166 | 			## Otherwise, use whatever we grabbed as the interpreter (might be .py, .pl, etc)
167 | 			scriptExt=$(echo "${shellEnv}" | sed 's/^M//')
168 | 		fi
169 | 	else
170 | 		## We didn't see a shebang as the first line, so assume its a shell script. Set the extension to .sh
171 | 		scriptExt="sh"
172 | 	fi
173 | 	## Now echo the entire script contents to a new file, using the display name and whatever extension we set
174 | 	echo "${ea_Script}" > "${scriptDownloadDir}/${ea_Name}.${scriptExt}"
175 | 	echo "Downloaded script \"${ea_Name}.${scriptExt}\"..."
176 | 	let downloadCount+=1
177 | 	
178 | done < <(echo "${allExtAttrIDs}")
179 | 
180 | echo "Finished downloading all Extension Attribute scripts from the JSS"
181 | 
182 | echo "Step 3:	Cleaning up script file contents...
183 | 	Adding ea_display_name line to end of each file (if needed)...
184 | 	Cleaning up ^M carriage returns in script contents...
185 | 	Setting executable flag for all script files..."
186 | 
187 | ## Loop through all downloaded scripts, stripping out problem characters and adding the ea_display_name line
188 | while read downloadedScript; do
189 | 	scriptBaseName="${downloadedScript%.*}"
190 | 	## Replace '&lt' with proper '<' symbol in script contents
191 | 	sed -i '' 's/&lt;/</g' "${scriptDownloadDir}/${downloadedScript}"
192 | 	## Replace '&amp' with proper '&' symbol in script contents
193 | 	sed -i '' 's/&amp;/\&/g' "${scriptDownloadDir}/${downloadedScript}"
194 | 	## Remove all Windows carriage returns (^M) from the script contents
195 | 	perl -pi -e 'tr/\cM//d;' "${scriptDownloadDir}/${downloadedScript}"
196 | 	## If the script doesn't already contain a #ea_display_name line, add one using the base file name
197 | 	if [[ ! $(grep "#ea_display_name" "${scriptDownloadDir}/${downloadedScript}") ]]; then
198 | 		echo -e "\n\n#ea_display_name	${scriptBaseName}" >> "${scriptDownloadDir}/${downloadedScript}"
199 | 	fi
200 | 	## Make sure all the scripts have the executable flag set for them
201 | 	chmod +x "${scriptDownloadDir}/${downloadedScript}"
202 | done < <(ls -p "${scriptDownloadDir}" | grep -v /)
203 | 
204 | echo "Step 4:	Running all downloaded scripts to check output..."
205 | 
206 | ## Create a directory for any scripts with problems (if needed)
207 | if [[ ! -d "${scriptDownloadDir}/Problem_scripts/" ]]; then
208 | 	mkdir "${scriptDownloadDir}/Problem_scripts/"
209 | fi
210 | 
211 | ## Create a directory for any scripts that fail (if needed)
212 | if [[ ! -d "${scriptDownloadDir}/Failed_scripts/" ]]; then
213 | 	mkdir "${scriptDownloadDir}/Failed_scripts/"
214 | fi
215 | 
216 | ## Run through each downloaded script, echo result and check exit status and output
217 | successCount=0
218 | failCount=0
219 | problemCount=0
220 | while read finalScript; do
221 | 	echo "Running script:	\"$finalScript\""
222 | 	scriptResult=$("${scriptDownloadDir}/$finalScript" 2>/dev/null)$?
223 | 	if [[ "$?" == "0" ]]; then
224 | 		finResult=$(echo "$scriptResult" | sed -e 's/<result>//;s/<\/result>0//')
225 | 		echo -e "Script result:	${finResult}"
226 | 		if [[ $(echo "${finResult}" | egrep "\*|<*>|,|%" ) ]]; then
227 | 			echo -e "PROBLEM:	The script \"$finalScript\" ran successfully but contains some known illegal characters that will cause the update to fail.\nPlease check the script output."
228 | 			echo "Moving \"$finalScript\" to Problem_scripts directory..."
229 | 			mv "${scriptDownloadDir}/$finalScript" "${scriptDownloadDir}/Problem_scripts/"
230 | 			let problemCount+=1
231 | 		else
232 | 			echo "PASSED:		The script \"$finalScript\" appears to have been successful..."
233 | 			let successCount+=1
234 | 		fi
235 | 	else
236 | 		echo "FAILED:		The script \"$finalScript\" exited with error code ${scriptResult}..."
237 | 		echo -e "Script error code:	$scriptResult"
238 | 		failure="yes"
239 | 		let failCount+=1
240 | 		echo "Moving \"$finalScript\" to Failed_scripts directory..."
241 | 		mv "${scriptDownloadDir}/$finalScript" "${scriptDownloadDir}/Failed_scripts/"
242 | 	fi
243 | 	echo -e "\n"
244 | done < <(ls -p "${scriptDownloadDir}" | grep -v / | egrep ".sh$|.pl$|.py$")
245 | 
246 | ## Display final results
247 | if [[ -z "$failure" ]] && [[ "$problemCount" == "0" ]]; then
248 | 	echo -e "\nFinal results:
249 | A total of ${downloadCount} scripts were downloaded.
250 | Congratulations! All ${downloadCount} scripts ran successfully!
251 | However, you may want to check the output for each script to verify that the results are what you expect."
252 | 
253 | elif [[ "$failure" == "yes" ]] && [[ "$problemCount" == "0" ]]; then
254 | 	echo -e "\nFinal results:
255 | A total of ${downloadCount} scripts were downloaded.
256 | ${successCount} scripts ran successfully.
257 | ${failCount} scripts exited with a failure code.
258 | Failed scripts have been moved to a sub directory called \"Failed_scripts\""
259 | 
260 | elif [[ "$failure" == "yes" ]] && [[ "$problemCount" != "0" ]]; then
261 | 	echo -e "\nFinal results:
262 | A total of ${downloadCount} scripts were downloaded.
263 | ${successCount} scripts ran successfully.
264 | ${failCount} scripts exited with a failure code.
265 | Failed scripts have been moved to a sub directory called \"Failed_scripts\"
266 | ${problemCount} scripts passed, but may have illegal characters in their results. Please check the script output above (Look for \"PROBLEM\")
267 | Problem scripts have been moved to a sub directory called \"Problem scripts\""
268 | 
269 | elif [[ -z "$failure" ]] && [[ "$problemCount" != "0" ]]; then
270 | 	echo -e "\nFinal results:
271 | A total of ${downloadCount} scripts were downloaded.
272 | All ${downloadCount} scripts passed, but $problemCount scripts have illegal characters in their results. Please check the script output above (Look for \"PROBLEM\")"
273 | 
274 | fi
275 | 
276 | echo -e "\nStep 5:	Done!"
277 | 
278 | exit
279 | 


--------------------------------------------------------------------------------
/update-extension-attributes.sh:
--------------------------------------------------------------------------------
  1 | #!/bin/bash
  2 | 
  3 | ## Script name:		update-extension-attributes.sh
  4 | ## Author:		Mike Morales (mm2270 on JAMFNation)
  5 | ##			https://jamfnation.jamfsoftware.com/viewProfile.html?userID=1927
  6 | ## Last change:		2014-05-14
  7 | 
  8 | ## Description:		Script to update any Extension Attribute values based on scripts located
  9 | ##			in a specified directory, by using the Casper Suite API
 10 | 
 11 | ## Casper Suite API assignments
 12 | ##
 13 | ## Hardcode the API username/password and JSS URL below, or, assign Casper Suite script parameters
 14 | ## for each item to have them passed down to the script at execution time
 15 | 
 16 | apiUser=""		## Assign Parameter 4 if using Casper Suite script parameter
 17 | apiPass=""		## Assign Parameter 5 if using Casper Suite script parameter
 18 | jssURL=""		## (Optional - see below) Assign Parameter 6 if using Casper Suite script parameter
 19 | 			## Special note: The script will use the following priority order to assign the JSS URL:
 20 | 			## 1)	If the JSS URL is hardcoded into the script it will be used first
 21 | 			## 2)	If the JSS URL variable is empty in the script and a Casper Suite parameter is
 22 | 			##		assigned for parameter 6, it will be used
 23 | 			## 3)	If the JSS URL variable is empty in the script and no Casper Suite parameter has
 24 | 			##		been assigned, the script will attempt to get the JSS URL from the client's
 25 | 			##		com.jamfsoftware.jamf.plist file.
 26 | 			## 4)	If the JSS URL variable is empty in the script, there is no Casper Suite parameter
 27 | 			##		assigned, and the script cannot get the JSS URL from the client, the script will
 28 | 			##		exit with an error since any upload of the resulting xml will be impossible.
 29 | 			##
 30 | 			## If you assign the JSS URL, either hardcoded or by script parameter, leave off the
 31 | 			## trailing slash from the string. Ex: "https://my.jssserver.com:8443"
 32 | 
 33 | ## Set the following variable to "yes" if its required to have the Mac check to see if
 34 | ## it is on your internal network.
 35 | ## Explanation : This will be required in cases where you have a Limited Access JSS.
 36 | ## Although the JSS Connection test will pass, an API upload attempt will fail because Tomcat
 37 | ## is required, which is disabled on the external WebApp instance.
 38 | ## If your JSS is openly accessible from the outside, you can leave this setting blank.
 39 | ##
 40 | ## Note: You must also specify either an internal http address or hostname to check for
 41 | ## internal connection verification in the next variable.
 42 | 
 43 | internal_check_req="yes"
 44 | 
 45 | ## If internal_check_req is set to yes, enter an internal address (hostname or http URL) the
 46 | ## script can use for checking internal connectivity.
 47 | ## Some examples of what you can enter are full http://www. style URLs (http://www.school.org),
 48 | ## or a base hostname (school.org). Be sure what you enter is accurate or it may result in
 49 | ## false failures, which will cause the script to exit.
 50 | 
 51 | ## You may also assign parameter 7 to the script in Casper Suite for the internal_address variable.
 52 | 
 53 | internal_address=""		## Assign Parameter 7 if using Casper Suite script parameter
 54 | 
 55 | ## OPTIONAL: Set the following to:
 56 | ## a) path to the base directory that contains the extension attribute scripts
 57 | ## b) path to the final xml file to be used in the API PUT upload.
 58 | ## You may also leave these as is.
 59 | ## Be sure to drop your EA script files into the basePath directory at the top level
 60 | basePath="/Library/Application Support/JAMF/extension_attributes"
 61 | xmlDir="/Library/Application Support/JAMF/extension_attributes_xml"
 62 | 
 63 | ################################ DO NOT EDIT BELOW THIS LINE ################################
 64 | 
 65 | function get_ea_results ()
 66 | {
 67 | 
 68 | ## Make sure the xml result directory exists. If not, create it
 69 | if [[ ! -d "$xmlDir" ]]; then
 70 | 	mkdir "$xmlDir"
 71 | fi
 72 | 
 73 | ## Set the xml path for the upload based on the directory assignment
 74 | xmlPath="${xmlDir}/ea_updates_xml.xml"
 75 | 
 76 | ## Get the MAC address for en0 on this Mac
 77 | MacID=$( /usr/sbin/networksetup -getmacaddress en0 | awk '{print $3}' | sed 's/:/./g' )
 78 | 
 79 | ## Generate the header of the xml file
 80 | echo "<?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"no\"?>
 81 | <computer>
 82 | <extension_attributes>" > "${xmlPath}"
 83 | 
 84 | ## Loop through each script in the base dir
 85 | while read ea_script; do
 86 | 	## Get the ea_display_name line from the scripts contents
 87 | 	ea_name=$(awk -F'[\t]' '/ea_display_name/{print $2}' < "$ea_script")
 88 | 	
 89 | 	ea_result=$("$ea_script" | sed -e 's/<result>//;s/<\/result>//')
 90 | 	if [[ ! -z "$ea_name" && "$ea_result" ]]; then
 91 | 	echo "<attribute>
 92 | <name>"${ea_name}"</name>
 93 | <value>$(echo "${ea_result}")</value>
 94 | </attribute>" >> "${xmlPath}"
 95 | 	fi
 96 | done < <(find "${basePath}" -maxdepth 1 -type f | egrep ".sh$|.pl$|.py$")
 97 | 
 98 | ## Finish off the xml file
 99 | echo "</extension_attributes>
100 | </computer>" >> "${xmlPath}"
101 | 
102 | ## Upload the final xml to the JSS
103 | echo "Finished collecting Extension Attribute results. Updating the computer record with new data..."
104 | curl -skfu "${apiUser}:${apiPass}" "${jssURL}/JSSResource/computers/macaddress/$MacID" -T "${xmlPath}" -X PUT
105 | uploadResult="$?"
106 | 
107 | ## Check the exit status of the upload
108 | if [[ "$uploadResult" == "0" ]]; then
109 | 	echo "API upload successful. Cleaning up and exiting..."
110 | 	## Delete the xml file after successful upload
111 | 	rm -f "${xmlPath}"
112 | else
113 | 	echo -e "API upload failed.\n\t1 - Check the \"ea_updates_xml.xml\" file located in \"${xmlDir}\" to make sure it was properly formed.\n\t2 - Check the network connectivity on this Mac."
114 | fi
115 | 
116 | }
117 | 
118 | ## Function for checking JSS availability
119 | function jss_check ()
120 | {
121 | 
122 | /usr/sbin/jamf checkJSSConnection -retry 2
123 | jss_check_result="$?"
124 | 
125 | if [[ "$jss_check_result" == "0" ]]; then
126 | 	echo "Move on to getting Extension Attribute results"
127 | 	get_ea_results
128 | else
129 | 	echo "JSS is not currently available. Exit the script"
130 | 	exit 0
131 | fi
132 | 
133 | }
134 | 
135 | ## Function for checking the internal network availability
136 | function internal_check ()
137 | {
138 | 
139 | if [[ "$checkType" == "ping" ]]; then
140 | 	echo "Running ping against ${internal_address}..."
141 | 	ping -c 2 -o "$internal_address" 2>&1 > /dev/null
142 | 	check_result="$?"
143 | elif [[ "$checkType" == "curl" ]]; then
144 | 	echo "Running curl against ${internal_address}..."
145 | 	curl -s -I "$internal_address"
146 | 	check_result="$?"
147 | fi
148 | 
149 | if [[ "$check_result" == "0" ]]; then
150 | 	echo "Internal check was successful. Move to checking JSS connectivity"
151 | 	jss_check
152 | else
153 | 	echo "Internal check failed. Exit the script."
154 | 	exit 0
155 | fi
156 | 
157 | }
158 | 
159 | ## Main script starts here
160 | ## Check and assign API information
161 | if [[ "$apiUser" == "" ]] && [[ "$4" != "" ]]; then
162 | 	apiUser="$4"
163 | else
164 | 	echo "Error: The apiUser variable was not defined in the script and no parameter was assigned."
165 | 	exit 1
166 | fi
167 | 
168 | if [[ "$apiPass" == "" ]] && [[ "$5" != "" ]]; then
169 | 	apiPass="$5"
170 | else
171 | 	echo "Error: The apiPass variable was not defined in the script and no parameter was assigned."
172 | 	exit 1
173 | fi
174 | 
175 | if [[ "$jssURL" != "" ]]; then
176 | 	jssURL="$jssURL"
177 | fi
178 | 
179 | if [[ "$jssURL" == "" ]] && [[ "$6" == "" ]]; then
180 | 	jssURL=$( defaults read /Library/Preferences/com.jamfsoftware.jamf jss_url | sed 's/\/$//' )
181 | elif [[ "$jssURL" == "" ]] && [[ "$6" != "" ]]; then
182 | 	jssURL="$6"
183 | else
184 | 	echo "Error: The jssURL variable was not defined in the script, no parameter was assigned and we were unable to pull the address from the client. Exiting..."
185 | 	exit 1
186 | fi
187 | 
188 | if [[ "$internal_address" == "" ]] && [[ "$7" != "" ]]; then
189 | 	internal_address="$7"
190 | fi
191 | 
192 | ## Find any shell, perl or python scripts in the source directory. Make sure there is at least one.
193 | if [[ $(find "${basePath}" -maxdepth 1 -type f -print | egrep ".sh$|.pl$|.py$") ]]; then
194 | 	echo "We have at least one extension attribute script to run"
195 | else
196 | 	echo "No extension attribute scripts were located"
197 | 	exit 0
198 | fi
199 | 
200 | ## Now check to see if the internal_check_req flag was set.
201 | ## If yes, assess the type of check we need to perform and run the internal check function.
202 | if [[ "$internal_check_req" == "yes" ]]; then
203 | 	echo "internal_check_req flag is set to \"yes\""
204 | 	if [[ "$internal_address" != "" ]]; then
205 | 		if [[ $(echo "$internal_address" | grep "^http") ]]; then
206 | 			checkType="curl"
207 | 			internal_check
208 | 		else
209 | 			checkType="ping"
210 | 			internal_check
211 | 		fi
212 | 	else
213 | 		## Exit if internal_check flag was set to yes and we didn't get an address to check against
214 | 		echo "No internal_address was specified in the script, but the internal_check_req flag was set. Enter an address to check and retry."
215 | 		exit 1
216 | 	fi
217 | else
218 | 	## internal_check_req was not set, so skip to the JSS check phase
219 | 	echo "No internal check required. Skipping to JSS Connection check"
220 | 	jss_check
221 | fi
222 | 


--------------------------------------------------------------------------------