Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Jul 25, 2024 10:53:53 AM
Feb 16, 2018 10:49:39 AM
All Qlik products are developed upon the security knowledge what was available to the of developing.
Content:
Note that enabling or disabling the correct protocols and ciphers has to be done on operating system level as our Qlik products rely on platform security. This can be done through registry edits or by using other third-party tools available to modify or view them with a graphical user interface.
QlikView and Qlik Sense in specific do not require any configuration to be done in the product. Qlik NPritning allows for some configuration, but Qlik NPrinting does not set a specific secure cipher suite as mandatory, in order to guarantee compatibility with different operating systems and platforms.
The following table shows QlikView support for SSL and TLS:
|
SSL v3.0 |
TLS v1.0 |
TLS v1.1 |
TLS v1.2 |
TLS v1.3 |
QlikView May 2023 up to current |
x |
x |
x |
x |
x |
QlikView 12.10 to May 2022 |
x |
x |
x |
x |
|
QlikView 11.20 SR16 |
x |
x |
x |
x |
|
QlikView 12.00 SR1 and later |
x |
x |
x |
x |
|
QlikView 12.00 |
x |
x |
|
|
|
QlikView 11.20 SR12 |
x |
x |
|
|
|
See Platform Security for your relevant Qlik NPrinting version.
Qlik Sense Enterprise on Windows: Certain internal only micro-services will still listen using TLS 1.0 / 1.1 in versions of Qlik Sense prior to Qlik Sense April 2018. Reference Defect: QLIK-85492 / Node.exe still listening to TLS1.0/1.1 or SSL even after disable them in Windows. This is resolved in Qlik Sense April 2018 (12.16.2), under a scan it would previously appear that TLS 1.0/1.1 is still using port 9090. Further Reading: Qlik Sense Ports not honoring TLS version prior to April 2018
IIS Crypto is an example 3rd party tool that can be used to achieve this. IIS Crypto is not supported by Qlik, but by its respective vendor, NARTAC Software. To obtain IIS Crypto, visit https://www.nartac.com/Products/IISCrypto.