Successfully setting Security by a (Custom) User Registry
and using a type 5 datasource results in the restarting the server
failure.
Security initialization fails for a: NamingException while looking up
datasource: jdbc/DSNAME
This error does not occur when security is set by the administrative
console.
The error message is:
I E SECJ0331E: The registry implementation file CustomRegistryImpl
cannot be initialized because of the following exception
com.ibm.websphere.security.CustomRegistryException: jdbc/WebAppDS at
CustomRegistryImpl.initialize(CustomRegistryImpl.java:149) at
com.ibm.ws.security.registry.UserRegistryImpl.initialize.
|
WebSphere Application Server does not support Custom
Registries that use Datasources because of initialization problems. JDBC
connections can be used to connect to a database in the custom registry
implementation.
Here is some relevant information from the information
center
In WebSphere Application Server Version 4.0, it might have been
possible to use other WebSphere Application Server components to
initialize the custom registry. For example, a datasource might have been
used to connect to a user registry database during the initialization of
the custom registry. You could also use EJBs deployed in WebSphere
Application Server during initialization. This is no longer possible in
WebSphere Application Server Version 5 since other components, like the
containers, are initialized after security and so are not available during
the registry initialization. Therefore, in Version 5, a custom registry
implementation is expected to be a pure custom implementation and should
not depend on other WebSphere Application Server components.
|