Configuring community synchronization using HTTPS

Since IBM® Connections authentication uses the HTTPS protocol, you must set up synchronization between IBM Sametime® Advanced and Connections communities using HTTPS.

Procedure

  1. Log in to the IBM WebSphere® Application Server Integrated Solutions Console of the Connections server.
  2. Click Security SSL Certificate and key management.
  3. Under Related Items, click Key store and certificates.
  4. Click NodeDefaultTrustStore.
  5. Under Additional Properties, click Signer Certificates.
  6. In the table, select the certificate that has a "default" alias issued to CN=connections_server_host,O=...., and then click Extract.
  7. Enter a file name, and click OK.
    Note: This file name is saved to the file system of the Connections Communities server.
  8. Log out of the Integrated Solutions Console of the Connections server.
  9. Copy the file containing the certificate from the Connections server file system to the Sametime server file system.
  10. Log in to the WebSphere Application Server Integrated Solutions Console of the Sametime Advanced server.
  11. Click Security SSL Certificate and key management.
  12. Under Related Items, click Key stores and certificates.
  13. Click NodeDefaultTrustStore.
  14. Under Additional Properties, click Signer Certificates.
  15. Click Add.
  16. Type an alias for the certificate, such as Connection Server Certificate.
  17. Type the path of the file where the certificate is saved.
  18. Click OK.
  19. Save the changes to the master configuration by clicking Save in the "Messages" box at the beginning of the page.