SSL and encryption

Communication between the CLC Server and its client software or between a master and its execution nodes can be configured to use HTTPS3.1.

In a new installation3.2, HTTPS communication between the CLC Server and its client software is supported out of the box using a self-signed certificate. See Client-server encrypted communication for details.

Configuring encrypted communication between a CLC Server master and its job nodes is described in Master-job node encrypted communication. Configuring encrypted communication between a CLC Server master and grid nodes is described in Master-grid node encrypted communication.

Helper tools are available from the CLC Server web administrative interface for managing and viewing certificates, and for editing Tomcat configuration files, e.g. to add or edit a Connector that supports encrypted communication. These helper tools also provide functionality aimed at supporting the use of self-signed certificates, such as adding certificates to the relevant trust stores when setting up encrypted communication between a master and execution nodes, and for creating self-signed certificates.


Footnotes

... HTTPS3.1
Support for encrypted communication between a master and its execution nodes was introduced in version 25.0.
... installation3.2
"New installation" means an installation of the CLC Genomics Server 25.0 or later to a new folder, as opposed to an upgrade in place from an earlier version of the software.

Subsections