IBM WebSphere V5.0 Security - CGISecurity

There is one point worth noting in regard to the difference between theinitialization of a WebSphere Application Server V5 custom registry and aWebSphere Application Server V4 custom registry. With Version 4, it waspossible to use other WebSphere Application Server components to initialize thecustom registry. For example, a datasource might have been used to connect toa database-based custom registry or one may have made use of a deployedEJB. However, in Version 5, both of these examples are not possible because,unlike in version 4, the security mechanism is initialised before other componentssuch as containers and therefore these facilities are not available when thesecurity component is started.WebSphereLTPAin te rfa ceLDAPuserregistrySecurityServerAuthenticateCallsLocal OSin te rfa ceLocal OSuserregistryPluggablecustomregistryCustomregistryFigure 8-1 Authentication registry mechanismsDeveloping a custom registryA sample custom registry implementation is provided with the application server.The custom registry class is called FileRegistrySample. The source code is alsoprovided for reference purposes. Refer to the InfoCenter for details onconfiguring the application server to use this.Some points should be taken into consideration when developing a customregistry.►►The com.ibm.websphere.security.UserRegistry interface must beimplemented. By implementing this interface, the super-interface,java.rmi.Remote, will also be implementedThe implementation should be compiled by adding the wssec.jar and idl.jarfiles to the classpath. These files can be found in the /libdirectory. 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