Scheduler.exe shows failed log on attempts in to the LDAP

This scenario will occur when the Qlik service account is a local user of the Qlik Server and users are populated from an LDAP.  

In Qlik Sense we need to get access to under information stored in user databases. One of the most common user databases that is used is LDAP. LDAP is a distributed database that is suitable to maintain user information in and is there for used both by opensource community (such as OpenLDAP) and in closed solutions (such as Microsoft LDAP).

The following describes the approach Qlik Sense takes to bring in user information.

In Qlik Sense we use a sync approach, this means that we replicate the user information including groups from the LDAP into our database and then keep these in sync. There are two use cases for using the user information, management and security.

For management it is good that the information is current but not absolutely critical so here we use the Qlik Sense scheduler to update the data. For security it is critical that information in current therefore we sync individual user records as the user connect to the Qlik Sense environment.

The benefit of a sync approach is that we can get quicker access to user information and are less dependent on the speed and reliability of the LDAP source. The downside is that we need to be able to fetch all information in one go.

 

Create a domain admin service account in the LDAP, then place it into the local admin account of the Qlik Server. 

NOTE: changing the service account has its own considerations that are not covered here. 
            At a minimum the following article should be considered. 
            https://qliksupport.force.com/articles/000049699