One scenario for using the LDAP server as a member repository is that you create a new instance of WebSphere Commerce and specify it to use an LDAP server as the member repository. In this scenario, you may need to modify the WebSphere Commerce bootstrap data for the Root Organization, Default Organization, and the 'wcsadmin' user entry, to match what is in your LDAP server.
For this scenario, you are required to complete the following:
- Create suffixes that are required in the directory server. User and organizational entity entries that will be used by WebSphere Commerce will exist under these suffixes.
- Create entries on the directory server for the 'Root Organization', 'Default Organization', and the site administrator user (for example, 'wcsadmin') with both 'Default Organization' and the site administrator user under the 'Root Organization'.
- Create a password in the LDAP server for the site administrator user entry.
- After the entries are created in the directory server, you should update the DN column in the ORGENTITY table with the correct distinguished names for the Root Organization (with MEMBER_ID -2001) and the Default Organization (with MEMBER_ID -2000).
- Set up the ldapentry.xml file for mapping WebSphere Commerce attributes to LDAP attributes. Ensure search bases for users are specified in the ldapentry.xmlfile such that the site administrator user can be found.
- Log on as the site administrator providing the proper password.
As more users are created on the directory server through WebSphere Commerce or another application, the users can log on WebSphere Commerce using either their RDN value or DN value. If users will logon using RDN, ensure search bases are specified properly in the ldapentry.xml file.
Note: If you create multiple instances of WebSphere Commerce and they share the same LDAP server, you should ensure the configuration for the LDAP server within each WebSphere Commerce instance is the same.