You can configure the Replication Server adapter to communicate with Replication Server over a secure connection using secure socket layers (SSL).
keytool –genkey –keyalg RSA –alias <keystore_alias> -keystore <keystore_path>\keystore.jks –storepass <keystore password> -validity 360 –keysize 2048
The values and requirements for the command parameters depend on the tool you use to generate the keystore; there are no ESP-specific requirements for these values. In the current example, the keystore location can use an absolute or relative path. The validity period is user-defined and expressed in number of days.
Ensure that the first and last name field of the key or certificate matches the name of the adapter connection definition in the RepServer sql.ini file. For example, if the adapter connection definition is ESP_RSAdapter, then the first and last name field for the key or certificate should be ESP_RSAdapter.
All other values, except for the key password, are optional.
keytool –exportcert –alias <keystore alias> -keystore <path to keystore.jks> -storepass <keystore password> -file <path to trusted.txt> -rfc
[espadapter] master=TCP,<hostname>,<port>,ssl query=TCP,<hostname>,<port>,ssl
Providing a greater-than-zero value to the TDS SSL port parameter enables SSL communication between the adapter and Replication Server. The regular TDS port parameter is still required, as that port is used by the adapter for internal communication. Therefore, when enabling SSL communication, the adapter uses 2 ports.
When you have configured SSL communication between the adapter and Replication Server, you can use SSL communication against ESP projects running in a cluster with SSL turned on by specifying the project URI adapter property with "esps://". This will achieve end-to-end SSL communication from Replication Server to the adapter to the ESP server.