IBM BS029ML Self Help Guide - Page 96
LDAP security problem determination, Multiple domains
View all IBM BS029ML manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 96 highlights
Note: Consult with your database server's documentation to confirm the correct format. Multiple domains If the DbUser, DbUrl, and DbPassword properties are not the same values across domains, the dbdomain.DataSourceName value should be changed for those domains that differ from the rest. The value for the dbdomain.DataSourceName should not be the same value as dbdomain.DbName. If you are unsuccessful after reviewing your configuration and using various support tools to help you debug, you may need to engage support. Refer to Appendix A, "Using IBM tools to find solutions and promote customer self-help" on page 169 for information about how to prepare your logs before engagement. 3.4.3 LDAP security problem determination This section shows some common problems with the enable security process, and provides you with some ideas on how to solve them. Failing to install the required and recommended fixes/Fix Packs for your platform One of the most common causes of security failures is not meeting the supported hardware or software requirements for your LDAP infrastructure. In addition to meeting the requirements for LDAP, you should ensure that all required and recommended fixes/Fix Packs WebSphere Portal Server have been installed for your platform (refer to 3.1.1, "How do I prepare my system for installation" on page 56). The fixes/Fix Pack issue is not isolated to the LDAP servers. Not applying the required fixes/Fix Packs for your portal environment can also cause errors during the enablement of security process and can affect the overall operability of your portal environment. To enable security, you should also ensure that you apply the latest WebSphere Member Manager fixes: http://www-1.ibm.com/support/docview.wss?rs=688&fdoc=wplcwspm&uid=swg24013740 Incorrect entries in the wpconfig.properties files This is perhaps the most common cause of errors with enabling LDAP security. The types of errors are usually attributed to the following: Typos or extra spaces: Be certain to look over your properties files for misspellings and extra spaces. Ensure that the values entered are the same case throughout. Running validation ldap targets before you conduct the enable security task may help you find some of the errors before you begin the procedure. Providing incorrect values for LDAP entries: Because the entries in the Advanced LDAP Configuration section are organization specific, validation ldap targets does not check these entries for errors. Take special care to ensure that the values entered here are correct for your LDAP design, as this is one of the most common causes of failure when enabling security. Verify that you can search for users and groups using the information specified in the Advanced LDAP Configuration using the ldapsearch utility. 82 IBM WebSphere Portal V6 Self Help Guide