"$"/bash/nxt_ra_script_output.shĪll write methods accept two arguments: the name of the output and the value to write. To use the functions in the Nexthink script for remote action output, add the following header at the beginning of your Bash scripts: The script includes functions to write results to the Engine. To that end, Nexthink provides a Bash script ( nxt_ra_script_output.sh) that is installed in the device of the employee at the same time as the Collector. The execution of a script may generate some outputs that you want to store as on-demand data in the Engine. Note that the actual values are always passed to the script as text: if the script declares parameters whose type is other than the string type, ensure that the values that you provide can be properly converted to the type of their corresponding parameter. Provide actual values to the parameters in the text input boxes displayed to the right of each parameter name. The editor of remote actions recognizes the parameters between the special Nexthink comments in a Bash script and lists them in the Parameters section, below the script text. The values for the parameters that a remote action passes to the script determine its actual behavior.ĭeclare parameters at the beginning of a script as usual for Bash positional parameters and enclose them between two special comments as follows: With parameters, the text of the script remains unchanged and thus the digital signature remains valid. By making a signed script generic, you allow its customization via parameters. When a script is signed, any modification to its text content breaks the signature. Genericity is especially useful in the case of digitally signed scripts that require some customization. Provide actual values to the parameters in the Finder, when editing the remote action that holds the script. To make your script generic, declare formal parameters at the beginning of the Bash script. Scripts may be written in a generic way so they can be adapted to particular use cases. Package your script and signature as a tar.gz file to preserve the extended attributes before uploading to the Finder:
#ACT FOR MAC CODE#
force Forces to rewrite a code signature if it already exists.
#ACT FOR MAC MANUAL#
See the code signature identifier generation rules in the codesign manual page.
Attaches your company identity to an identifier and helps to make an identifier unique. prefix A prefix to a code signature identifier. timestamp Generate a trusted timestamp for a signature.
#ACT FOR MAC FULL#
See the codesign manual page for the full description. Usually, it's a certificate subject common name or a certificate hash. s The identity of your code signing certificate in the Keychain. Finder only accepts files with tar.gz extension when importing scripts for remote actions that target macOS.Ĭodesign -s -timestamp -prefix= -force Additionally, package your signed script as a tar.gz file to preserve its extended attributes.
#ACT FOR MAC MAC#
To write your own Bash scripts for remote actions, encode the files that hold the text of your scripts in UTF-8 (without BOM).Įnd each line in the code with the usual character in UNIX systems: LF.įailing to provide the right encoding to your script files will result in the inability of remote actions to run on the devices of the employees.įor security reasons, the Finder requires Bash scripts for remote actions on Mac to be digitally signed with the codesign tool. Remote actions group in Community Encoding This article assumes familiarity of the reader with Bash scripting.įind more information about writing scripts for remote actions on Community:
#ACT FOR MAC HOW TO#
Learn here the specifics of how to write Bash scripts for remote actions. Bash scripts are therefore ideal to get on-demand data from devices, perform self-healing tasks, or modifying the configuration of a device, which are typical use cases for remote actions. Bash is a command-line shell and scripting language that is supported by many UNIX-like operating systems, such as macOS, and suited for task automation and configuration management. The payload of remote actions on Mac are Bash scripts that run on the devices of the employees. Writing scripts for remote actions on Mac Overview 1.6.2 Running a campaign from the script of a remote action.1.6 Interacting with end-users in self-help scenarios.1.3 Signing and packaging your own scripts.1 Writing scripts for remote actions on Mac.Importing and exporting authored content.Writing scripts for remote actions on Mac.Writing scripts for remote actions on Windows.Tracking the execution of remote actions.Continuously measuring the satisfaction of employees.Limiting the reception rate of campaigns.Specifying URL paths of web-based services.
Graphically observing the activity of users and devices.Visualizing system activity in the Finder.Navigating through the results of an investigation.Combining logical conditions in investigations.Editing the options of an investigation.
0 kommentar(er)
