|
Problem(Abstract) |
For this instance after re-booting the machine customer
was not able to start any Application Server running on the node and the
following exceptions were being thrown into SystemOut.log file:
[5/1/06 10:25:13:748 EDT] 4e3b113a UserRegistryI A SECJ0136I: Custom
Registry:com.ibm.ws.security.registry.ldap.LdapRegistryImpl has been
initialized
[5/1/06 10:25:14:226 EDT] 4e3b113a LTPAServerObj E SECJ0238E: An
unexpected exception occurred when trying to create the initial
LTPAServerObject. The exception is java.lang.NullPointerException
at com.ibm.ws.security.ltpa.LTPAPrivateKey.decode(LTPAPrivateKey.java:57)
at
com.ibm.ws.security.ltpa.LTPAPrivateKey.<init>(LTPAPrivateKey.java:47)
[5/1/06 10:25:20:703 EDT] 4e3b113a WsServer E WSVR0003E: Server
WebSphere_Portal failed to start
com.ibm.ws.exception.RuntimeError
at
com.ibm.ws.security.core.ServerSecurityComponentImpl.start(ServerSecurityComponentImpl.java:204)
at
com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:536)
Caused by: com.ibm.websphere.security.WSSecurityException
at
com.ibm.ws.security.auth.ContextManagerImpl.getServerSubject(ContextManagerImpl.java:1784)
at
com.ibm.ws.security.auth.ContextManagerImpl.initialize(ContextManagerImpl.java:271)
... 18 more
Caused by: com.ibm.websphere.security.auth.WSLoginFailedException
at
com.ibm.ws.security.server.lm.ltpaLoginModule.login(ltpaLoginModule.java:425) |
|
|
|
Cause |
LTPAToken keys are corrupted. |
|
|
Resolving the
problem |
If global security is already enabled and the server is
not starting, then refer to Changing
security settings in IBM® WebSphere® Application Server with
wsadmin for more information on disabling global security using
the wsadmin.sh/bat command line tool
- Log into the administrative console > Security > Authentication
Mechanisms > LTPA.
- Generate a new set of keys by clicking on "Generate Keys" button.
- Save and synchronize changes.
- Re-enable global security from the console and re-start the
servers.
- Now you should be able to start the server and log into console
successfully.
|
|
|