IBM WebSphere V5.0 Security - CGISecurity

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