For general tips on diagnosing and resolving security-related problems, see the topic Troubleshooting the security component.
If you do not see a problem that resembles yours, or if the information provided does not solve your problem, contact IBM support for further assistance.
"LTPA password not set. validation failed" message displayed as error in the Administrative Console after saving global security settings
"Validation failed for user userid. Please try again..." displayed in the Administrative Console after saving global security settings
The setupClient.bat or setupClient.sh file is not working correctly
The setupClient.bat file on Windows platforms and the setupClient.sh file on UNIX platforms incorrectly specify the location of the SOAP security properties file.set CLIENTSOAP=-Dcom.ibm.SOAP.ConfigURL=file:%WAS_HOME%/properties/soap.client.props
CLIENTSOAP=-Dcom.ibm.SOAP.ConfigURL=file:$WAS_HOME/properties/soap.client.props
Java HotSpot Server VM warning: Unexpected Signal 11 occurred under user-defined signal handler 0x7895710a message occurs in the native_stdout.log file when enabling security on the HP-UX11i platform
Java HotSpot(TM) Server VM warning: Unexpected Signal 11 occurred under user-defined signal handler 0x7895710aTo work around this error, apply the fixes recommended by HP for Java at the following URL: http://www.hp.com/products1/unix/java/infolibrary/patches.html.
WebSphere Application Server Version 6 is not working correctly with Enterprise Workload Manager (EWLM)
grant codeBase "file:/<EWLM_Install_Home>/classes/ARM/arm4.jar" { permission java.security.AllPermission; };Otherwise, you might encounter a Java 2 security exception for violating the Java 2 security permission.
Refer to Configuring server.policy files for more information on configuring server.policy files.
For current information available from IBM Support on known problems and their resolution, see the IBM Support page.
IBM Support has documents that can save you time gathering information needed to resolve this problem. Before opening a PMR, see the IBM Support page.
NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation
NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow: If you use CSIv2 inbound authentication, basic authentication is required, and Java™ clients running with com.ibm.CORBA.validateBasicAuth=true might fail with the following exception: NMSV0610I: A NamingException is being thrown from a javax.naming.Context implementation. Details follow: Context implementation: com.ibm.ws.naming.jndicos.CNContextImpl Context method: lookupExt Context name: TestaburgerNode01Cell/nodes/TestaburgerNode01/servers/server1 Target name: SecurityServer Other data: "" Exception stack trace: javax.naming.NoPermissionException: NO_PERMISSION exception caught. Root exception is org.omg.CORBA.NO_PERMISSION: vmcid: 0x49421000 minor code: 92 completed: No ... SECJ0395E: Could not locate the SecurityServer at host/port:9.42.72.27/9100 to validate the userid and password entered. You may need to specify valid securityServerHost/Port in (WAS_INSTALL_ROOT)/properties/sas.client.props file.
To fix this problem, modify the com.ibm.CORBA.validateBasicAuth=false property in the clients.sas.clients.props file and then run the client.
Related tasks
Troubleshooting by task
Troubleshooting by component