This article explains the functional requirement for drwxrwxrwt permissions on the Workload Automation Agent spool directory. These settings are frequently flagged during security audits or vulnerability (VUL) scans. This configuration is necessary to prevent access-denial issues in multi-user job execution environments where multiple designated users run jobs through the agent.
Product: CA Workload Automation System Agent
OS: Unix / Linux
Releases: ALL
When the System Agent runs as the root user and executes jobs on behalf of different owners, the specific job owner must have write and execute access to the spool folder to create and update their individual spool files. If the spool directory is restricted, the job owner will be unable to access the folder, leading to job failures or stuck statuses.
The spool folder requires world-writable and executable permissions (777) with the sticky bit (t) enabled.
Technical Justification
Implementation
Run the following command to ensure the spool directory is correctly configured:
The resulting permissions should appear as follows:
Managing Individual File Permissions
If security scans flag the permissions of the files created within the spool folder, use the following parameters in agentparm.txt to enforce stricter file-level access:
oscomponent.umask: Defines the default umask for jobs and the agent.oscomponent.defaultfile.permission: Sets the default permissions for files created by the agent (e.g., 640).For detailed steps on configuring these parameters, see Change the Default Permissions of the Files Created by the Agent.