Skip to main content
Announcements
Marching toward a simplified navigation! READ ON
cancel
Showing results for 
Search instead for 
Did you mean: 
VRaducan
Partner - Contributor III
Partner - Contributor III

X509N:<S>CN=QlikClient failed to log in because it is unknown in the domain

Good Morning,

We have 2 customers complaining that they keep receiving an error on the QlikClient Certificate stating: 

The user X509N:<S>CN=QlikClient failed to log in because it is unknown in the domain. The login attempt was made from the host  "ip of the host". 

Also the same problem appeared here some time ago but other that upgrading there are no other instructions :https://community.qlik.com/t5/Deployment-Management/User-or-certificate-X509N-lt-S-gt-CN-QlikClient-...

The 2 environments are different, one of Which is a fresh new Qlik Sense Installation November 2021 Patch4.  So it doesn't look like it's an "old release problem". 

The only thing in common of the 2 environments that we saw, was that they are using "CortexXDR" antvirus or endPoint Protection (some sort of).

We have tried configuring the config file as per this documentation: 

https://community.qlik.com/t5/Knowledge/Qlik-Sense-authentication-fails-with-X509N-Bad-User-Name-Log...

Customers stated that the logging entries appears to be less commonly logged but still, are present. 

Is there anything we can do about it? What's the component of Qlik Sense which uses this Certificate with this name? (I think it's something related to the PostgreSQL DB: the repository Service).

We've also got a screenshot from one of the customers and the account trying to log in with that certificate to the domain looks to be NT AUTHORITY\System.

Both Qlik Sense installation are single Node, and are working fine with no issues whatsoever. No Kerberos authentication forced on they're domain and just standard installation of Qlik Sense.

Any Advices? 

Thanks

Vlad Raducan 

ITREVIEW

 

 

Labels (1)
1 Solution

Accepted Solutions
Jaroslav_Stsetinin
Former Employee
Former Employee

Hello,

This issue has been raised with our Engineering teams and is under investigation. We fully reproduced the issue and working on fix. However, there is currently no time-estimate for resolution as there is no impact on core product functionality.

This reported issue ID is: QB-8542 to be used for tracking directly to our Community Page, kindly subscribe to receive notifications on the latest Release notes for patches and news releases.

If you have any functional impact on your deployment, please let us know.

 

View solution in original post

3 Replies
Jaroslav_Stsetinin
Former Employee
Former Employee

Hello,

This issue has been raised with our Engineering teams and is under investigation. We fully reproduced the issue and working on fix. However, there is currently no time-estimate for resolution as there is no impact on core product functionality.

This reported issue ID is: QB-8542 to be used for tracking directly to our Community Page, kindly subscribe to receive notifications on the latest Release notes for patches and news releases.

If you have any functional impact on your deployment, please let us know.

 

VRaducan
Partner - Contributor III
Partner - Contributor III
Author

 Ok, thank you.

Vlad Raducan

Simonanuri
Partner - Contributor
Partner - Contributor

Hi,

Any updates for the QB-8542?

We are in version NOV 22 and still have the same issue.

Thanks