Qlik does not issue trusted SSL certificates: There is a problem with this website's security certificate

Sonja_Bauernfeind · Sep 17, 2021 3:55:03 AM

Users accessing a newly installed Qlik product such as Qlik Sense, QlikView, or NPrinting via browser encounter a warning:

There is a problem with this website's security certificate

The warning may vary depending on the browser used:

Your connection is not private

NET::ERR_CERT_COMMON_NAME_INVALID

The warning indicates that the client does not trust the SSL certificate.

Qlik's products come with self-signed certificates. To fix the warning the system administrator needs to make sure the either:

(recommended) Obtain a valid Signed Server Certificate matching the Proxy node URL, from a trusted Certificate Authority (such as VeriSign, GlobalSign or trusted Enterprise CA) or your corporate certificate authority.
Trusts the served SSL certificate. This can be achieved using a Group Policy, see Distribute Certificates to Client Computers by Using Group Policy.

Before installing Qlik products, some decisions have to be made by the system administrator:

Is it necessary to enable SSL?
If YES, what type of SSL Certificate to use in this system?
1. - A certificate purchased from and signed by a trusted CA (Certificate Authority) such as VeriSign, Thawte, Geotrust, etc.
  - A certificate provided and signed by your own Enterprise CA (Certificate Authority).
  - And, of course, a self-signed one. Those can be created by any number of applications, such as Microsoft IIS, but is generally only recommended for test environments. More so, it has the potential side effect of teaching users to ignore browser warnings, which we do not want.