Symptoms

While configuring a new Security Label, we noticed that a LDAP request is sent to the LDAP directory every time there is a GetUserDetails call from the UMUser Smart Object.
This request is ending as timeout.
Here are examples of timeout requests :

>08/Jul/2016:15:13:14 +0200] conn=299244 op=1 SRCH base="o=TheCompany" scope=2 filter="(samaccountname=k2fruser)" attrs="primarygroupid objectsid"
>08/Jul/2016:15:30:24 +0200] conn=299258 op=1 SRCH base="o=TheCompany" scope=2 filter="(samaccountname=K2 User)" attrs="primarygrouptoken"
>08/Jul/2016:15:32:37 +0200] conn=299266 op=1 SRCH base="o=TheCompany" scope=2 filter="(samaccountname=K2 User)" attrs="primarygrouptoken"
>08/Jul/2016:15:33:06 +0200] conn=299270 op=1 SRCH base="o=TheCompany" scope=2 filter="(samaccountname=p066601)" attrs="primarygroupid objectsid"
>08/Jul/2016:15:34:55 +0200] conn=299273 op=1 SRCH base="o=TheCompany" scope=2 filter="(samaccountname=k2esuser)" attrs="primarygroupid objectsid"
 

Diagnoses

This issue appeared because the samaccountname was hard coded in the default
SourceCode.Security.Providers.LdapProvider.Trusted.dll
and
SourceCode.Security.Providers.LdapProvider.dll
 

Resolution

ColdFix provided.