User ID should not be encoded using PropFilePasswordEncoder
 Technote (troubleshooting)
 
Problem(Abstract)
The stopManager or stopServer command fails if the user ID is encoded with PropFilePasswordEncoder.
 
Cause
If security is enabled , the user ID and password must be passed as argument to stop the server. To avoid typing the user ID and password, both can be specified in the Install_Root/properties/soap.client.props file.

The password specified in the soap.client.props can be encoded using PropFilePasswordEncoder. The user ID in the soap.client.props should not be encoded. If it is encoded, the stopmanager fails with an "insufficient or empty credentials" error message.

 
Resolving the problem
PropFilePasswordEncoder should be used only to encode the password in the properties file; the user ID should not be encoded. Change the encoded user ID back to unencrypted text.
 
Related information
WebSphere Application Server V5.0.x: Security and Scri
 
 
Cross Reference information
Segment Product Component Platform Version Edition
Application Servers Runtimes for Java Technology Java SDK
 
 


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > Administrative Console (all non-scripting)
Operating system(s): Windows
Software version: 5.1.1.3
Software edition:
Reference #: 1198303
IBM Group: Software Group
Modified date: Sep 28, 2007