[IBM i]

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.

Before you begin

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

About this task

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:

Procedure

  1. Sign on the server with a user profile that has all object (*ALLOBJ) special authority.
  2. Run the Start Qshell (STRQSH) command on a command line to start the Qshell environment.
  3. 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 WebSphere Application Server profile (in a default installation), enter the following command:
    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 the following command:
    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.

Results

The passwords are encoded in the soap.client.props and sas.client.props files.

What to do next

See Restoring or replacing damaged validation list objects for information on how to restore or replace a damaged validation list object.