Importing a certificate to support SSLAdded by IBM on May 8, 2014 | Version 1 (Original)
|Import a certificate so that IBM Connections and WebSphere Portal can communicate over Secure Socket Layer (SSL).
In order for WebSphere Portal to communicate with IBM Connections over Secure Sockets Layer (SSL), the WebSphere Portal Server must trust the signer of the SSL certificate for IBM Connections. This might be set up by default in your WebSphere infrastructure if you use SSL certificates that are issued by a commonly recognized authority. If you use self-signed certificates, the default certificate or a signer that is not recognized by your WebSphere Portal Server, you must import the SSL certificate from IBM Connections to your WebSphere Portal Server.
Import the SSL keys into the Portal server as follows:
Parent topic: Deploying the IBM Connections Portlets
- Log in to the WebSphere® Application Server Integrated Solutions Console.
- Navigate to Security -> SSL certificate and key management -> Key stores and certificates.
- Add the certificates to the appropriate truststore as configured in SSL Configurations. To view the SSL configuration and determine the appropriate truststore, navigate to: Security -> SSL certificate and key management -> SSL configurations -> NodeDefaultSSLSettings -> ['Trust Store Name']
For example, in a stand-alone deployment you navigate to NodeDefaultTrustStore -> Signer certificates for adding certificates. If NodeDefaultSSL Settings points to 'CellDefaultTrustStore', you add a certificate to 'CellDefaultTrustStore'.
Note: In a clustered deployment, add certificates for all Portal nodes to the Connections nodes, and add certificates for the Connections nodes to the Portal nodes.
- Click Retrieve from port.
- Enter the host and SSL port that is used by your Connections server.
The default SSL port is 443. Give the alias a name, for example, Connections
. For example:
- Click Retrieve signer information.
- Click OK.
- Click Save.