Application Triggers

another way to have client applications work with dynamically changed passwords is by restarting the client apps with the new passwords after an account password has been changed application triggers are defined for this purpose when defined, the password vault connects to the server running the client apps and restarts the apps with the new password to define application triggers navigate to secrets > application management open the application triggers t ab click on to add button select the vault account used to trigger a restart after the account password change select the configuration select the target type as either single device or bulk select a device if you selected single device target type, or select the device group and the element type if bulk target type is selected and click save according to the rule in the application trigger definition, trigger name , vault account , and parameter name values cannot be defined with the same values multiple times when an account password changes and an application trigger is set off, a trigger processes record is created for each matching device, associated with the relevant application trigger definitions to search for these process records, use the trigger processes tab navigate to secrets> application management open the trigger processes tab select the desired process click to continue the initial status of this process is waiting to trigger this process at a specific time, the aapmtriggerprocessjob job must be defined in the jobs scheduler navigate administration > jobs scheduler open the trigger list tab select aapmtriggerprocessjob as the job fill in the trigger name and cron expression fields to enable the job, select enabled for the active field and click save regardless of how many triggers are set, running only one trigger process job is enough to run all triggers to define the aapm strategy navigate to secrets>configuration open the application configuration tab click the options button to show properties define the properties