Setting up single sign-on (SSO) with the IBM Connections server

You must set up SSO between the Sametime® Meeting Server and the Connections Files server. Both the Meeting Server and the Connections server must use the same LDAP directory.

About this task

You first need to create an LTPA key on the Sametime Meeting Server, and then you will import that key onto the Connections Files server.

Procedure

  1. Log in to the Integrated Solutions Console for the Meeting Server as the WebSphere® administrator. If you are in a clustered environment, log in to the deployment manager.

    For example: log in to https://meetingserverhostname/ibm/console/

  2. Click Security > Global Security, and then in the Authentication section, click LTPA.
  3. In the Cross-cell single sign-on section, enter a password and file name for the LTPA key. Remember this information; the file that is created will be imported on the Connections Files server.
  4. Click Generate Keys and then click Export.
  5. Save the changes to the master configuration by clicking Save in the "Messages" box at the beginning of the page.
  6. When the Synchronize changes with Nodes window displays, click OK.
  7. Click Security > Global Security, and then in the Authentication section, click WEP and SIP SecuritySingle Sign-on (SSO).
  8. Make sure that the Domain name is correct for your Meeting Server, and that interoperability mode is selected. Click OK.
  9. Save the changes to the master configuration by clicking Save in the "Messages" box at the beginning of the page.
  10. Open the Connections Files server as the WebSphere Administrator.
  11. Click Security > Global Security, and then in the Authentication section, click LTPA.
  12. In the "Cross-cell single sign-on" section, enter the password for the LTPA key you created.
  13. Enter the file name and path to the LTPA key. This is the location you exported the new key to.
  14. Click Import Keys.
  15. Restart the Connections Files server.