Develop custom user registries

WAS security supports the use of custom registries in addition to Local OS and LDAP registries for authentication and authorization purposes. A custom user registry is a customer implemented user registry which implements the UserRegistry Java interface as provided by WAS. A custom implemented user registry can support virtually any type or notion of an accounts repository from a relational database, flat file, and so on. The custom user registry provides considerable flexibility in adapting WAS security to various environments where some notion of a user registry, other than LDAP or LocalOS, already exist in the operational environment.

Implementing a custom user registry is a software development effort. Use the methods defined in the UserRegistry interface to make calls to the desired registry to obtain user and group information. The interface defines a very general set of methods, for encapsulating a wide variety of registries. You can configure a custom user registry as the active user registry when configuring WebSphere Application Server global security.

Verify that your implementation of the custom registry does not depend on any WAS components such as data sources, enterprise beans, and so on. Do not have this dependency because security is initialized and enabled prior to most of the other WebSphere Application Server components during startup. If your previous implementation used these components, make a change that will eliminate the dependency. For example, if your previous implementation used data sources to connect to a database, use Java database connectivity (JDBC) to connect to the database.

For backward compatibility, the WAS Version 4 custom on migrating. If your previous implementation uses data sources to connect to a database, change the implementation to use Java database connectivity (JDBC) connections. However, it is recommended that you use the new interface to implement your custom registry.

  1. If not familiar with the custom user registry concept, refer to the article, Custom user registries.This section explains each of the methods in the interface in detail and the changes for these methods from the version 4 release.

  2. Implement all the methods in the interface except for the CreateCredential method, which is implemented by WAS. A sample that implements this interface is provided for reference.

  3. Build your implementation.You need the %$WAS_HOME%/lib/sas.jar and %$WAS_HOME%/lib/wssec.jar files in your class path. For example: %$WAS_HOME%\java\bin\javac -classpath %$WAS_HOME%\lib\wssec.jar;%$WAS_HOME%\lib\sas.jar

  4. Copy the class files generated in the previous step to the product class path.The preferred location is the %$WAS_HOME%/lib/ext directory. This should be copied to all the product processes (cell, all NodeAgents) class path.

  5. Follow the steps in Configuring custom user registries to configure your implementation using the administrative console.


Usage Scenario

If you enabling security, make sure you complete the remaining steps. Once this is done, make sure you save and synchronize the configuration and restart all the servers. Try accessing some J2EE resources to verify that the custom registry implementation is successful.


See Also

Custom user registries
Configuring custom user registries
UserRegistry interface methods files file for WAS v5 and V5.1 file for WAS v5.0.2
Custom user registry settings