The Windows Security log records authentication errors for an account with name X509N:<S>CN=QlikClient
, citing Failure Reason: Unknown user name or bad password
The Active Directory log will record the same.
No symptoms are seen in the daily operation of Qlik Sense. Environment:
(reported in, but not restricted to)
Qlik Sense June 2017 Patch 2
Qlik Sense February 2018
Qlik Sense April 2018
Qlik Sense June 2018
The root cause of this behaviour, is Windows attempting to authenticate the QlikClient certificate as a user, but no such user exists.
This is a known problem, and was addressed starting from version September 2018 release of Qlik Sense.To active the fix the setting "EnableDotNetWebSockets" in the app.config file (C:\Program Files\Qlik\Sense\Repository\Repository.exe.config) must be set to true. If the Qlik Services are running using a non local administrator account then bootstrapping needs to be run after the changed configuration. The fix is not supported by Windows 7
A possible workaround in the meantime, is to configure Windows to map the QlikClient certificate to a user. A good candidate for such a user would be the Qlik Sense service account user.
Instructions for this can be found with Microsoft
. These changes need to be made on the Domain Controller.