IBM WebSphere V5.0 Security - CGISecurity

group membership, and other group and user information whichWebSphere requires access to. For our administrator, the fully qualifiedDN we entered iscn=Websphere Administrator,ou=tamral,dc=tivoli,dc=svo,dc=dfw,dc=ibm,dc=com.– Bind Password: enter the password for your WebSphere administrator.Click OK.3. The Global Security panel will be displayed. Enable global security, scrolldown and in the Active User Registry field, and select LDAP.4. Click the OK button.5. Your updates will now be validated; if no errors are found, save yourconfiguration.6. Restart your WebSphere server, and start the WebSphere AdministrativeConsole. You will now be prompted to enter a user ID and password.You have now completed the configuration of WebSphere using Active Directoryas its user registry.Testing LDAP connectionsThere are cases when you can run into difficulties when configuring WebSphereto use LDAP directory as a user registry. In these cases, the first step is to isolatethe problem by testing your LDAP connection.For testing, you should try to connect to the LDAP server from the WebSpheremachine. Test the LDAP connection without security, then test the connectionwith security (LDAPS) if you are planning to use that.For testing purposes, you can use any LDAP client on the server machine, theldapsearch command line utility from the IBM Directory Server distribution (partof the client), the ldapsearch command line utility from Lotus Domino, Netscapeor Mozilla’s address book search, or Microsoft Outlook (Express) address booksearch.When you are testing the connection, make sure you provide the binding dn withthe password. When testing the secure connection (LDAPS), make sure youhave the LDAP server’s public certificate installed or provided as a parameter forthe client; if client-side authentication is configured, import the client certificateinto the LDAP server’s keyring.490 IBM WebSphere V5.0 Security Handbook