Help needed to unserstand our issue with the Filtering about ldapcp

[Yvand]

The filtering is done in LDAPCP.ProcessLdapResults() method.
There can be a lot of reasons why a result is removed by the filtering.
If you want, you can clone the source code, download the
symbols from LDAPCP_Debug.zip and live debug to find out why it is excluded.
It's heavy but it will work...

[Yvand]

Hi @eduralph, did you figure out what was wrong?

[eduralph]

Hi Yvand,

thanks for following up. The issue was occuring in the production environment and we were hesitant to install a Debug version, so we couldn't drill as deep as we would have liked. Ultimately, it was an issue with a) the network connection to the AD Servers or b) the responses the AD Servers were bringing back. We could never really figure that one out as the issue vanished after a couple of days.
So, it wasn't LDAPCP but it would have been nice to be able to see the return responses and the specific filter which was applied in the logs (maybe verbose?) to understand the issues.

[Yvand]

Hi @eduralph, there are too many reasons to filter out a potential result to record that in SharePoint logs, even in Verbose(Ex):
LDAPCP parses each LDAP attribute of each LDAP result, and keep only relevant values (to transform in PickerEntity result) based on many criteria.
In case you want to take a look, this logic is implemented in method LDAPCP.ProcessLdapResults()