What causes this?
- Recent NodeJS security risk resolutions in Qlik Sense resulted in fixes in Qlik Sense that cause internal certificates to be replaced/updated.
- These Qlik Sense updates result in the necessity to re-export Qlik Sense certificates from Qlik Sense and insert them accordingly as described in the resolution section of this article.
Environments Affected
- Qlik Sense November 2019 and earlier versions which are upgraded to Qlik Sense February 2020 and later versions
- NPrinting (All versions) connected to Qlik Sense
Resolution
Using the Qlik Sense QMC, export your Qlik Sense server certificates from each additional Qlik Sense server.
- Use the NPrinting server name as the "machine name"
- Select include secret key and
- Do NOT include a password when exporting the certificates. See Exporting certificates through the QMC on the Qlik Sense Online Help for details.
- Reference
Next, If June 2019 NPrinting or later versions are is in use, do the following:
- Navigate to the exported certificates location on the QS server and rename the exported file 'client.pfx' with a suitable name. ie: if your Qlik Sense server name is QS1, prepend the file client certificate file name as follows: QS1client.pfx (Naming of this file should ideally reflect the Qlik Sense server that the file was exported from. You may use however, any name that you wish)
- Copy this file to the NPrinting server path: "C:\Program Files\NPrintingServer\Settings\SenseCertificates"
- Restart all NPrinting services
If April 2019 NPrinting (no longer supported) or earlier versions are in use, please follow the certificate import steps outlined in Installing Qlik Sense certificates
