Introduction › How Local Security Works

How Local Security Works

You must define a user ID and password on the scheduling manager that is registered with the HP Integrity NonStop system. For example, you must use the Manage user@host users option of the autosys_secure command to define the user ID and password on CA Workload Automation AE and the PASSWORD command on CA Workload Automation ESP Edition.

This user ID and password are validated on the agent using the HP Integrity NonStop API named USER_AUTHENTICATE. This validation is optional for the password and is controlled by the WLA-PASSW-REQUIRED parameter in CAOPTS, the agent configuration file.

The HP Integrity NonStop file system provides a built-in access mechanism to the job executable file or script. If a user executes a job and does not have execute or read permissions, a file system error (48) is displayed, indicating a security violation. When this occurs, the job goes into a SUBERROR state and is sent back to the submitting scheduling manager.