IBM WebSphere V5.0 Security - CGISecurity

There is one point worth noting in regard to the difference between the
initialization of a WebSphere Application Server V5 custom registry and a
WebSphere Application Server V4 custom registry. With Version 4, it was
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 database-based custom registry or one may have made use of a deployed
EJB. However, in Version 5, both of these examples are not possible because,
unlike in version 4, the security mechanism is initialised before other components
such as containers and therefore these facilities are not available when the
security component is started.
WebSphere
LTPA
in te rfa ce
LDAP
user
registry
Security
Server
Authenticate
Calls
Local OS
in te rfa ce
Local OS
user
registry
Pluggable
custom
registry
Custom
registry
Figure 8-1 Authentication registry mechanisms
Developing a custom registry
A sample custom registry implementation is provided with the application server.
The custom registry class is called FileRegistrySample. The source code is also
provided for reference purposes. Refer to the InfoCenter for details on
configuring the application server to use this.
Some points should be taken into consideration when developing a custom
registry.
►
►
The com.ibm.websphere.security.UserRegistry interface must be
implemented. By implementing this interface, the super-interface,
java.rmi.Remote, will also be implemented
The implementation should be compiled by adding the wssec.jar and idl.jar
files to the classpath. These files can be found in the /lib
directory. The following command should be used to compile the registry:
/java/bin/javac -classpath
/lib/wssec.jar:/lib/idl.jar
184 IBM WebSphere V5.0 Security Handbook