Prepare a SecureWay Security Server
If you plan to use a SecureWay Security Server as an LDAP user registry, you must install and set up the server so that it communicates with HCL Digital Experience.
Procedure
-
Install SecureWay Security Server. Refer to IBM® SecureWay™ Security Server for z/OS® and OS/390® for information.
-
Complete the following steps with the web administration tool to create the HCL Portal administrative user:
-
Complete the following steps to create a directory suffix:
- Click the Server Administration folder in the directory server console navigation.
- Click the Manage Server Properties folder under the Server Administration folder and then select Suffixes on the main page.
- Type the Base DN name for the suffix; for example: dc=yourcompany,dc=com.
- Click Add.
- Click OK to save your changes.
-
Open the appropriate LDIF file in the PortalServer_root/installer/wp.iim/ldif directory, with a text editor:
- Use the PortalUsers.ldif file as a working example and adapted appropriately to work with your LDAP server.
- Use the ContentUsers.ldif file for the IBM Content Manager group and user ID if you configured HCL Web Content Manager.
-
Replace every dc=yourco,dc=com with your suffix.
-
Replace any prefixes and suffixes that are unique to your LDAP server.
-
You can specify user names other than wpsadmin and wpsbind. For security reasons, specify nontrivial passwords for these administrator accounts.
-
Save your changes.
-
Complete the instructions that are provided with your directory server to import the LDIF file.
-
-
Complete the following steps to create the HCL Portal administrative user:
-
Complete the following steps to create a directory suffix:
- Go to IBM System i and IBMi Information Center, select the appropriate documentation version and go to Networking > TCP/IP applications, protocols, and services > IBM Directory Server for iSeries (LDAP) > Administering Directory Server > General administration tasks > Adding and Removing Directory Server suffixes for information.
- Stop and restart the LDAP server.
-
Open the appropriate LDIF file in the PortalServer_root/installer/wp.iim/ldif directory, with a text editor:
- Use the PortalUsers.ldif file as a working example and adapted appropriately to work with your LDAP server.
- Use the ContentUsers.ldif file for the IBM Content Manager group and user ID if you configured HCL Web Content Manager.
-
Replace every dc=yourco,dc=com with your suffix.
-
Replace any prefixes and suffixes that are unique to your LDAP server.
-
You can specify user names other than wpsadmin and wpsbind. For security reasons, specify nontrivial passwords for these administrator accounts.
-
If you use IBM Security Access Manager Version 5.1, set the objectclasses to accessGroup. If you use Security Access Manager Version 6, set the objectclasses to par.
-
Save your changes.
-
Complete the instructions that are provided with your directory server to import the LDIF file.
-