following a misconfiguration, I found when binding with the AD, the connection was successfully established,
but often when doing the search, it found that the type was not correct and it jumps and destroys the connection.
But he didn't tell me anything, what message can be put on it for a better guide?
DEBUG:flask_ldap3_login:Opening connection with bind user 'user'
DEBUG:flask_ldap3_login:Successfully bound to LDAP as 'user' for search_bind method
DEBUG:flask_ldap3_login:Performing an LDAP Search using filter '(&(objectclass=user)(sAMAccountName=user))', base 'dc=domain,dc=com', and scope 'SUBTREE'
DEBUG:flask_ldap3_login:Destroying connection at <0x7f8e95d9fb38>
following a misconfiguration, I found when binding with the AD, the connection was successfully established, but often when doing the search, it found that the type was not correct and it jumps and destroys the connection. But he didn't tell me anything, what message can be put on it for a better guide?
'type': 'searchResRef'
Validation