During installation, if you chose the HTTPS protocol, Agent for IBM Lotus Domino 6.5.4 is automatically configured and ready to communicate over SSL. Before proceeding with the following tasks in this section, ensure that IBM Lotus Domino 6.5.4 is configured for SSL.
You should have a solid understanding of SSL concepts and the security certificates required to enable communication over the HTTPS protocol. See the documentation for the IBM Lotus Domino 6.5.4 server.
Add the IBM Lotus Domino 6.5.4 certificate’s root CA certificate to the Access Manager’s certificate database.
Mark the CA root certificate as trusted to enable Access Manager to successfully send notifications to Agent for IBM Lotus Domino 6.5.4.
This section only applies when Access Manager itself is running SSL. By default, the agent installed on a remote IBM Lotus Domino 6.5.4 instance will trust any server certificate presented over SSL by the Access Manager host. The web agent does not check the root Certificate Authority (CA) certificate. If the Access Manager host is SSL-enabled and you want the agent to perform certificate checking, adhere to the guidelines as described in the following subsections:
The following property in the web agent AMAgent.properties configuration file controls the agent’s trust behavior, which by default it is set to true:
With this property set to true, the web agent does not perform certificate checking. On Linux systems, enabling the web agent to perform certificate checking is a one-step process that only involves setting this property to false as illustrated in the following task.
Set the following property in the web agent AMAgent.properties configuration file to false as follows:
com.sun.am.trust_server_certs = false
The root CA certificate that you install on the remote instance of IBM Lotus Domino 6.5.4 must be the same certificate that is installed on the Access Manager host.