Developing stand-alone custom registries
This development provides considerable flexibility in adapting WebSphere® Application Server security to various environments where some notion of a user registry, other than LDAP or Local OS, already exists in the operational environment.
Before you begin
WebSphere Application Server security supports the use of stand-alone custom registries in addition to the local operating system registry, stand-alone Lightweight Directory Access Protocol (LDAP) registries, and federated repositories for authentication and authorization purposes. A stand-alone custom-implemented registry uses the UserRegistry Java™ interface as provided by WebSphere Application Server. A stand-alone custom-implemented registry can support virtually any type or notion of an accounts repository from a relational database, flat file, and so on.
Implementing a stand-alone custom registry is a software development effort. Implement the methods that are defined in the com.ibm.websphere.security.UserRegistry interface to make calls to the appropriate registry to obtain user and group information. The interface defines a general set of methods for encapsulating a wide variety of registries. You can configure a stand-alone custom registry as the selected repository when configuring WebSphere Application Server security on the Global security panel.
In WebSphere Application Server Version 8.5, make sure that your implementation of the stand-alone custom registry does not depend on any WebSphere Application Server components such as data sources, Enterprise JavaBeans (EJB) and Java Naming and Directory Interface (JNDI). You can 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 eliminates the dependency. For example, if your previous implementation used data sources to connect to a database, instead use the JDBC java.sql.DriverManager interface to connect to the database.
If your previous implementation uses data sources to connect to a database, change the implementation to use Java database connectivity (JDBC) connections.
Procedure
Example
Viewing stand-alone custom registries.
Use these links to view registry examples.
A stand-alone custom registry is a customer-implemented registry that implements the UserRegistry Java interface, as provided by WebSphere Application Server. A custom-implemented registry can support virtually any type or form of an accounts repository from a relational database, flat file, and so on. The custom registry provides considerable flexibility in adapting WebSphere Application Server security to various environments where some form of a registry, other than a federated repository, Lightweight Directory Access Protocol (LDAP) registry, or local operating system registry, already exist in the operational environment.
What to do next
- Save and synchronize the configuration and restart all of the servers.
- Try accessing some J2EE resources to verify that the custom registry implementation is correct.