Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

---

 

Set up Tivoli Directory Server

Use the information in this topic to set up IBM^® Tivoli^® Directory Server as your LDAP server.

 

Overview

This topic contains information on creating a new portal administrative user in Tivoli Directory Server and configuring a secure connection to the LDAP server. Use the following steps as a guide to set up your environment.

• Creating a new user as the portal administrator

  • Creating a new user for Windows and Linux

  • Creating a new user for i5/OS

• Example of the Tivoli Directory Server structure

 

Create a new user as the portal administrator

Creating a new user for Windows and Linux

Use the following steps if the portal administrative user does not exist in Tivoli Directory Server. These directions also assume that you are creating a new directory suffix for this user. If you already have a directory suffix, skip steps 1 through 3 and begin with step 4:

1. In the Tivoli Directory Server console, click the Server Administration folder on the left-hand navigation. Click the Manage Server Properties folder underneath it, and then click on the Suffixes link on the right-hand side of the main page.

2. Type the name of the Base DN to be used as the suffix, for example, dc=yourco,dc=com. Click Add to add the suffix.

3. When you are finished adding the suffix, click OK to save your changes.

4. Stop and start the LDAP server.

5. If you choose to use the LDIF file, locate PortalUsers.ldif in the root directory on the CD Setup, and open it in a text editor.

   Notes:

   • The PortalUsers.ldif file is provided as a working example and needs to be adapted appropriately to work with your LDAP server.

   • If you have configured IBM DB2^® Content Manager, there is a separate LDIF file. Use ContentUsers.ldif for the DB2 Content Manager group and user IDs.

6. Replace all occurrences of dc=yourco,dc=com with the suffix that you are using.

7. Replace any prefixes and suffixes that are unique to your LDAP server. You can specify user names other than wpsadmin and wpsbind if you want. For security reasons, you should specify non-trivial passwords for these administrator accounts because it is easier to specify them now than to change them after installation.

8. Optional: If using IBM Tivoli Access Manager for e-business Version 5.1, set the objectclasses to accessGroup. If using Tivoli Access Manager Version 6, set the objectclasses to groupOfNames.

9. Save your changes.

10. Follow the instructions provided with your Tivoli Directory Server to import PortalUsers.ldif.

    Importing the PortalUsers.ldif file could overwrite existing user data.

11. Stop and restart the LDAP server.

12. After the installation, if you did not specify non-trivial passwords for the administrator IDs in the LDIF file, it is recommended that you change the passwords for these user IDs. See Changing passwords in the IBM WebSphere Portal Express information center for instructions.

Creating a new user for i5/OS

You will need to create a portal administrative user if one does not already exist. It is assumed that you are creating a new directory suffix for this user. If you already have a directory suffix, you can skip the instructions for creating one.

1. For instructions on how to create a suffix, see the Add suffixes to the LDAP directory server topic in the System i5 information center.

2. Stop and start the LDAP server. Skip this step if you did not just create a directory suffix for the portal administrative user.

3. If you choose to use the LDIF file, locate PortalUsers.ldif in the root directory on the CD Setup, and open it in a text editor.

   1. Replace all occurrences of dc=yourco and dc=com with the suffix that you are using.

   2. Replace any prefixes and suffixes that are unique to your LDAP server. You can specify user names other than wpsadmin and wpsbind if you want.

   3. Pre-Portal installation: For security reasons, you should specify non-trivial passwords for these administrator accounts because it is easier to specify them now than to change them after installation.

      Post-portal installation: If you did not specify non-trivial passwords for the administrator IDs in the LDIF file, it is recommended that you change the passwords for these user IDs. Follow the instructions in Changing passwords.

   4. For instructions on how to import LDIF files, see the Import an LDIF file topic in the System i5 information center.

For additional information on the Tivoli Directory Server, refer to the topic in the System i5 information center.

 

Example of the Tivoli Directory Server structure

The following schema is an example for Tivoli Directory Server and is referenced throughout the documentation for consistency. The example below is designed to help you determine the appropriate values when configuring WebSphere Portal Express to work with your specific directory layout. The values shown match the default values for this LDAP. If you have an existing schema that varies from this example, replace the example values with your values. For instance, cn is shown as the group prefix; replace cn with the group prefix for your schema.

LDAP suffix="dc=yourco,dc=com" user prefix="uid" user suffix="cn=users" group prefix="cn" group suffix="cn=groups" Portal administrator DN="uid=wpsadmin,cn=users,dc=yourco,dc=com" Portal administrator group="cn=wpsadmins,cn=groups,dc=yourco,dc=com"

 

Parent topic:

Tivoli Directory Server

 

Previous topic

Creating required LDAP users and groups

 

Next topic

Disabling global security

---