Manually encoding passwords in properties files

(iSeries)
Manually encoding passwords in properties files

To use password encoding with WebSphere Application Server administrative commands and Java clients, passwords must be manually encoded in the soap.client.props and sas.client.props files using the PropFilePasswordEncoder tool.

To run the script, your user profile must have *ALLOBJ authority.

Use the PropFilePasswordEncoder utility to encode the passwords in properties files. The PropFilePasswordEncoder utility is a Qshell script. Complete the following steps to manually encode the passwords:

Tasks
Sign on the server with a user profile that has all object (*ALLOBJ) special authority.
Run the Start Qshell (STRQSH) command on a command line to start the Qshell environment.
Use the PropFilePasswordEncoder utility to encode the passwords.
For example, to encode the passwords for properties in the sas.client.props file for the default WAS profile (in a default installation), enter:
 profile_root/bin/PropFilePasswordEncoder 
 -profileName server1 
  profile_root/properties/sas.client.props -SAS
For example, to encode the passwords for properties in the soap.client.props file for the default stand-alone application server profile, enter:
 profile_root/bin/PropFilePasswordEncoder 
 -profileName server1 
  profile_root/properties/soap.client.props 
 com.ibm.SOAP.loginPassword,com.ibm.ssl.keyStorePassword,
 com.ibm.ssl.trustStorePassword
For more information on the sas.client.props utility, see the PropFilePasswordEncoder command reference.
The passwords are encoded in the soap.client.props and sas.client.props files.

What to do next
See Restore or replace damaged validation list objects for information on how to restore or replace a damaged validation list object.

Related:

Password encoding and encryption
Change encoding algorithm from OS400 to XOR
Enable the non-default OS/400 password encoding algorithm
Restore or replace damaged validation list objects
Password decoding troubleshooting tips for security