Configuring WebSphere with Tivoli Directory Server federated repositories

You must complete some additional steps when configuring Content Platform Engine to run on WebSphere® with Tivoli® Directory Server federated repositories. If you are not using federated repositories, or if Tivoli Directory Server is configured to use inetOrgPerson for logins, skip these steps.

To configure WebSphere with Tivoli Directory Server federated repositories:

1. In WebSphere administrative console, navigate to Security > Global security. Under the User account repository, select Federated repositories and click Configure.
2. Under Related items, click Manage repositories, select the federated repository, click LDAP entity types, and then click PersonAccount.
3. Change inetOrgPerson to the Object class attribute (for example, the person attribute) by which your Tivoli Directory Server users log in.
4. Find your WebSphere profile file wimconfig.xml. Typically, this file is at /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/YourNode01Cell/wim/config and open it for editing:
   1. Search wimconfig.xml for the string userPassword that is located in the following stanza:

      <config:attributeConfiguration>
      <config:attributes name="userPassword" propertyName="password"/>
      <config:attributes name="krbPrincipalName" propertyName="kerberosId">
      <config:entityTypes>PersonAccount</config:entityTypes>
      </config:attributes>

   2. Immediately after the stanza that you located in the preceding substep, add the following stanza:

      <config:attributes name="login_attribute" propertyName="login_property">
      <config:entityTypes>PersonAccount</config:entityTypes>
      </config:attributes>

      In the stanza you added, replace login_attribute with the Tivoli Directory Server attribute by which users log in; and replace login_property with the value you specified in the Login properties field (cn is the default value; other possible values are uid and sn).

   3. Save your edits.
5. Restart the application server instance on which you are deploying Content Platform Engine.