search cancel

Some User Passwords Created/Updated with autosys_secure CLI do not get stored properly


Article ID: 201631


Updated On:


CA Workload Automation AE - Scheduler (AutoSys) CA Workload Automation AE


When creating a new user or updating an existing user's password using the command line arguments for autosys_secure such as...

autosys_secure -c -u [email protected] -o old_password -p new_password

...the password sometimes does not store properly in the database. It gets modified in some way, but not to the value specified on the command line.


Release : 11.3.6, 12.0

Component : CA Workload Automation AE (AutoSys)


This behavior can occur when the password you are specifying contains a character that has special meaning to the shell in which you are running the autosys_secure command. The shell will modify the password value due to the special characters before it is passed to the Application Server to be stored in the database. For example...

A user's password is modified to NewPa$$word...

autosys_secure -c -u [email protected] -o old_password -p NewPa$$word

In the bash shell, $$ has special meaning. It gets substituted with a PID of the process running the command that contains it. Therefore, prior to that password value getting passed to the Application Server, the bash shell would substitute the $$ with the PID of the bash shell process and the resulting password that is stored in the database will be modified.


When the password contains special characters that could have special meaning to the shell, put single quotes around it to avoid the problem...

autosys_secure -c -u [email protected] -o old_password -p 'NewPa$$word'