Using SSL to encrypt connections to a Helix server
The following sections explain how you set up encrypted communications between a client and a Helix server.
For any given Helix server, proxy, or broker, SSL encryption is an all-or-nothing option: If a Helix server is configured to use SSL (presumably for security reasons), all Helix server applications must be configured to use SSL. Conversely, if a Helix server is configured to accept plaintext connections (either for performance reasons or for backwards compatibility), all client applications must connect in plaintext. It is possible however, if you have an intermediary (such as a proxy or a broker) between the client and the Helix server, that one leg of the communication is encrypted and the following is not. For more information, see Using SSL in a mixed environment.
For details on supported version and configuration, see the Knowledge Base article, "SSL and TLS Protocol Versions".