Since IBM® Connections authentication
uses the HTTPS protocol, you must set up synchronization between IBM Sametime® Advanced and Connections
communities using HTTPS.
Procedure
- Log in to the IBM WebSphere® Application Server
Integrated Solutions Console of the Connections server.
- Click SSL Certificate and key management.
- Under Related Items, click Key store and certificates.
- Click NodeDefaultTrustStore.
- Under Additional Properties, click Signer Certificates.
- In the table, select the certificate that has a "default"
alias issued to CN=connections_server_host,O=....,
and then click Extract.
- Enter a file name, and click OK.
Note: This file name is saved to the file system of the Connections
Communities server.
- Log out of the Integrated Solutions Console of the Connections
server.
- Copy the file containing the certificate from the Connections
server file system to the Sametime server file system.
- Log in to the WebSphere Application
Server Integrated Solutions Console of the Sametime Advanced server.
- Click SSL Certificate and key management.
- Under Related Items, click Key stores and certificates.
- Click NodeDefaultTrustStore.
- Under Additional Properties, click Signer Certificates.
- Click Add.
- Type an alias for the certificate, such as Connection
Server Certificate.
- Type the path of the file where the certificate is saved.
- Click OK.
- Save the changes to the master configuration by clicking Save in
the "Messages" box at the beginning of the page.