Configure a bind user ID

The bind user ID is used by LotusCollaborative Services to retrieve user attributes required for authentication from the selected LDAP directory. Setting the bind user ID to use the LDAP server for Collaborative Services supports automatic detection of users' mail files for any of the collaborative portlets that use a Lotus Dominobackend server for messaging (Lotus Notes View and iNotes). If the server is a Lotus Domino LDAP, setting the bind user also supports the server or database dropdown lists that appear in Lotus Domino portlets.

Before you set up the bind user, the WebSphere Portal server must be configured to recognize Collaborative Services (a previous task in this sequence). If you choose not to configure Collaborative Services to bind to the Lotus Domino LDAP, you can, instead, enable access to certain Lotus Domino fields by anonymous users. For information on setting the HTTP-HostName and HTTP-Port fields as queriable fields in the Configuration Settings document on the Lotus Domino LDAP server, see the topic on setting a Domino LDAP server to allow anonymous access.

To set the bind user, edit the CSEnvironment.properties file.

Perform the following steps:

  1. Stop WebSphere Portal:

      cd WP_PROFILE/bin
      ./stopServer.sh WebSphere_Portal -username admin_userid -password foo

  2. Edit...

      WP_PROFILE/PortalServer/config/CSEnvironment.properties

    Make a backup copy of the file before making changes.

  3. Locate the following section in the file:

      # Add Default IIOP/SSL Port

  4. Under the heading in the previous step, remove the comment tag (#) from the beginning of the line that contains...

      CS_SERVER_DOMINO_DIRECTORY_1.userid=

  5. At the end of the line, add a user ID that has appropriate access in the LDAP directory that supports Collaborative Services. Type the Lotus Domino LDAP fully qualified. For example, for the name of the user...

      cn=domino admin,ou=orgunit,o=org

      On a Lotus Domino LDAP server, this user ID must have at least reader access to the address book names.nsf file. For a non-Lotus Domino LDAP directory, ask the LDAP administrator to provide a user with appropriate access to search the mailserver, mailfile, http-hostname, and http-port attributes.

  6. Go to the line that contains...

      CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd=

  7. Remove the comment tag (#) from the beginning of this line.

  8. Copy the line that contains CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd= and paste it into a new file.

  9. In the new file, at the end of the line, add the internet password for the user ID (that was entered for CS_SERVER_DOMINO_DIRECTORY_1.userid=).

  10. Save this new file as dominobind.txt in the WAS_HOME directory.

  11. Open a command prompt to the WAS_HOME/bin}}} directory.

  12. In the same directory, run the following command (type as one line with a space character separating it):

      PropFilePasswordEncoder dominobind.txt CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd

  13. In the same directory, open the dominobind.txt file, and copy the encrypted password after CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd=.

  14. Go back to the CSEnvironment.properties file.

  15. Paste the encrypted password after:

      CS_SERVER_DOMINO_DIRECTORY_1.encryptedpwd=

  16. Save and close the CSEnvironment.properties file.

  17. Close the dominobind.txt file, and then delete dominobind.txt and dominobind.txt.bak from the WAS_HOME/bin

  18. Start the WebSphere_Portal server

      cd WP_PROFILE/bin
      ./startServer.sh WebSphere_Portal


Parent

Give Collaboratives Services access to required fields for automatic mail detection

 


+

Search Tips   |   Advanced Search