This content has been marked as final. Show 4 replies
I found that error in console, but all the users can inquires in em.
So don't affect use . But the wrong let people unhappy ,if Can solve is very good.
I'm facing the same issue. Until now every user can connect but there must be a reason why this error occurs. Hopefully someone could solve that and share his solution.
I too face same issues few months back then I set the Look Through Limit to -1, which means search the entire directory
1). by Changing maximum results option using ldapconn.setOption(LDAPv2.SIZELIMIT,25000)
2. Changing Look Through Limit to around 25000 in ldap server.
The final success of the configuration, and does not need to modify AD :
User Base DN: DC=abc,DC=com
All Users Filter:
Users From Name Filter: (&(cn=%u)(objectclass=user))
User Name Attribute: sAMAccountName
User Object Class: user
Group Base DN: CN=Builtin,DC=abc,DC=com
All Groups Filter:
Group From Name Filter: (&(cn=%g)(objectclass=group))
Static Group Name Attribute: cn
Static Group Object Class: group
Static Member DN Attribute: member
Static Group DNs from Member DN Filter: (&(member=%M)(objectclass=group))
GUID Attribute: objectguid
EM Identity Store Provider: