TLS 1.2 protocol support has been integrated since June 2017. The Qlik License Service supports the following cipher suites:
- TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256
- TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384
- TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305
- TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305
- TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA
- TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA
- TLS_RSA_WITH_AES_128_GCM_SHA256
- TLS_RSA_WITH_AES_256_GCM_SHA384
- TLS_RSA_WITH_AES_128_CBC_SHA
- TLS_RSA_WITH_AES_256_CBC_SHA
- TLS_ECDHE_RSA_WITH_3DES_EDE_CBC_SHA
- TLS_RSA_WITH_3DES_EDE_CBC_SHA
Configuration Steps
To prioritize specific cipher suites for the Qlik License Service, follow this procedure:
-
Navigate to the configuration file named
service.conf.
The default installation path is:
%Program Files%\Qlik\Sense\ServiceDispatcher\service.conf -
Locate the configuration block labeled
[licenses.parameters]. It will initially resemble the following structure:[licenses.parameters] -qsefw-mode -app-settings="..\Licenses\appsettings.json" -
Inject the
-cipher-suitesargument into this section, providing a comma-separated list of the desired ciphers. The modified configuration should look similar to the example below:[licenses.parameters] -qsefw-mode -cipher-suites=TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA -app-settings="..\Licenses\appsettings.json" -
Save the changes and close the text editor.
-
Restart the Qlik Sense Service Dispatcher service, which manages the execution of the Qlik License Service, to apply the new settings.
-
In a multi-node deployment environment, ensure that these configuraton steps are replicated on every individual node.