Typical Security Configuration Problems - IBM BS029ML - WebSphere Portal Server Self Help Manual

Since PumaService is the base for WebSphere Portal security, its failure would cause the
portal server to fail.
ConfigTrace.log
This file contains important messages for all configuration tasks. It should never be discarded.
The Portal configuration command-line tool WPSconfig.bat/.sh is an extension of the Apache
Ant build tool. It calls Java classes, Database SQL scripts, Jacl scripts through wsadmin (a
WebSphere command-line utility), or an XMLaccess command-line utility to configure various
parts of WebSphere Portal and WebSphere Application Server. It signals the success or
failure of a configuration task or actions by issuing either a BUILD SUCCESSFUL or BUILD
FAILED message at the end.
Typical error messages in runtime logs
All portal error message codes are in the format of "EJPxxnnnnE". Normally, when you see a
portal error, there may be some errors from the WebSphere Application Server side.

4.3.6 Typical security configuration problems

In this section, we provided several typical problem scenarios. This is not intended to be a
complete set of all security problems. We only want to provide several cases that are often
encountered and provide suggestions on how to try to resolve them.
Cannot start servers after security was enabled
The two most likely causes of startup failure are due to database connection or a
configuration in security. For this section, we only concentrate on the latter. In most cases, the
failure is due to the failed authentication of the WebSphere Application Server administration
user.
Using LDAP tools, like an LDAP browser or ldapsearch, try to verify that the LDAP bind user is
able to access the LDAP, and the WebSphere Application Server admin user's DN and
password is correct. Then check the baseDN (LDAP suffix) and user filter definition in
WebSphere Application Server global security are set correctly. Since the server is not
started, you may have to edit the security settings directly in security.xml. With WebSphere
Application Server, security trace enabled,
When the server could not be started, it is likely that the WebSphere Admin user had failed at
authentication. If the password might have been changed, or the company security policy had
required the password to be changed, this would cause the authentication failure of the
WebSphere administrative user ID, as shown in the following case:
[8/12/07 15:32:12:672 EDT] 00000017 WSMM Message E
com.ibm.ws.wmm.ldap.LdapConnectionImpl void initialize(Map envProperties)
Initialization failed. Root cause is:
"javax.naming.AuthenticationException: [LDAP: error code 49 - 80090308: LdapErr:
DSID-0C090334, comment: AcceptSecurityContext error, data 52e, vece ]".
[8/12/07 15:32:12:812 EDT] 00000017 WSMM Message E
com.ibm.ws.wmm.objectimpl.MemberServiceBeanBase ejbCreate()
java.lang.NullPointerException
[8/12/07 15:32:12:875 EDT] 00000017 ExceptionUtil E
unexpected (non-declared) exception during invocation of method
"getConfigurationData". Exception data:
com.ibm.ejs.container.CreateFailureException: ; nested exception is:
java.lang.reflect.InvocationTargetException
122
IBM WebSphere Portal V6 Self Help Guide
CNTR0019E: EJB threw an