IBM WebSphere V5.0 Security - CGISecurity

Method signature
Result getUsersForGroup(String
groupSecurityName, int limit) throws
NotImplementedException,
EntryNotFoundException,
CustomRegistryException,
RemoteException
public List getGroupsForUser(String
userSecurityName) throws
EntryNotFoundException,
CustomRegistryException,
RemoteException
Credential createCredential(String
userSecurityName) throws
NotImplementedException,
EntryNotFoundException,
CustomRegistryException,
RemoteException
Use
Gets a list of users in a group. The
maximum number of users returned is
defined by the limit argument.
Gets all the groups the given user is a
member of.
Throws the NotImplementedException for
this method.
Sample custom registry
The following section documents the implementation of a DB2 custom registry.
The DB2 registry uses JDBC to communicate with the database. Although this
registry was tested with DB2, it should be possible to modify it to work with other
relational databases. The source code (DB2Registry.java) is shown below and is
also included in the ITSOBank application, along with the database structure.
Open the DB2Registry.java source in WebSphere Studio and check the
comments in the source code. You will find all the required methods for the
UserRegistry interface implemented. Look for the SQL queries in the code and
see what each method does with the database,
The DB2Registry.class file must be copied to a directory accessible by the
application server, that is a directory that is in the application server’s classpath
(for example, /lib). Alternatively, update the application
server’s classpath to refer to the directory that contains the class file.
A simple custom registry test utility that runs from the command line is included
and can be used to test whether the custom registry is working as required. The
tool allows the developer to be sure that the custom registry is functioning before
configuring the application server to use it. The tool will ask for some user and
group information and use this information to query the custom registry. It will
Chapter 8. Programmatic security 189