IBM WebSphere V5.0 Security - CGISecurity

6. In the Configuration tab provided, fill out the following values as mentioned
below.
7. From the Active User Registry drop-down list select LDAP as the active user
registry when security is enabled.
Figure 10-10 LDAP is the Active User Registry
8. Click Apply; this will validate the settings.
Note: In case the validation fails for any reason, go back to the LDAP
configuration panel and check your settings again.
9. Save the configuration for WebSphere, then restart the server.
Testing the connection
When the server starts, launch the Administrative Console; it should ask for a
user name and password for authentication. This is because Global Security is
enabled. Provide the user name and password as cn=wasadmin,o=itso and
password as password. If you are able to log in successfully, that means your
configuration is working fine.
Note: If the user ID field is set for the user in the LDAP directory, then you can
use the user ID for user name authentication, in this case: wasadmin.
For the IBM SecureWay Directory configuration and sample user and group
registration, refer to 10.13, “Connecting to directory servers (LDAP)” on
page 317.
10.4.3 Custom Registry
WebSphere can be configured to use a type of user registry other than LocalOS
and LDAP. This registry is referred to as a Custom Registry. It will be necessary
to provide a Java class that provides WebSphere with a standard interface in
order for WebSphere to communicate with the registry in an appropriate fashion.
Refer to 8.3, “CustomRegistry SPI” on page 183 for information regarding the
development of such an interface.
Open the Custom Registry window in the Admin console by selecting
Security -> User Registries -> Custom.
248 IBM WebSphere V5.0 Security Handbook