Open jwalstra-keeper opened 5 months ago
Hi, this is not related to ldap3 but to the response received from the server. Were you able to fix it?
I've seen this bug as well recently, it seems to happen when there is a cycle in referrals or for some reason a server refers to itself.
It seems like https://github.com/cannatag/ldap3/blob/86a9e7afedba7f7ca9eeb43710054abaf654539b/ldap3/strategy/base.py#L692 is supposed to protect against this recursion depth, but _referrals is never modified from what I can find, so it never uses this condition.
The more annoying part that I've run into is that the connections are not properly cleaned up when this happens, causing new sockets to be made and left open once the recursion depth is hit, eventually running my process out of file descriptors.
I'm performing a search for a user.
I'm getting the following error.
I know I could make a better filter by using person instead of a wild star. Could this be due to the configuration of the Active Directory server? I'm a programmer, not an AD admin. I also do not have access to the Active Directory.
Any help would most appreciated, John