Adaptive secure communication

Edit online

To reduce performance overhead for same-host deployments, you can disable SSL encryption for communication between the server and the object agent.

Before you begin

The server and object agent must be installed and configured. This setting applies only when the object agent and server are running on the same host system.

About this task

By default, the server and object agent communicate over TLS-encrypted TCP/IP sessions. When both components run on the same host, TLS encryption and decryption can create performance overhead, particularly on AIX.

When you set the encrypt parameter to false, the system verifies that the server and object agent are running on the same host. If both components are on the same host, TLS encryption is disabled for new sessions after initial sign-on and authentication. Sign-on and authentication always occur over encrypted sessions. If the components are running on different hosts, the parameter is ignored and TLS remains enabled.

Procedure

  1. Open the object_agent_config.json file.
  2. In the sessionPool section, set the encrypt parameter to false. 
    "sessionPool": {
  "maximumSize": 100,
  "timeout": 120000000000,
  "maximumWait": 120000000000,
  "maximumTime": 1680000000000,
  "useClientCache": true,
  "encrypt": false
}
  3. Save the file and restart the object agent.

Results

For new sessions, the system verifies whether the server and object agent are running on the same host. If both components are on the same host, TLS encryption is disabled after initial sign-on and authentication. If the components are running on different hosts, TLS remains enabled.