You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
After a successful bind, a search throws the Operations error. 000004DC: LdapErr: DSID-0C090A5C, comment: In order to perform this operation a successful bind must be completed on the connection.
To Reproduce
Any search on my particular setup would do. E.g
var connection = new LdapConnection();
connection.Connect($"ldap://192.168.1.10");
connection.Bind(Native.LdapAuthType.Simple.ToString(), username, password);
connection.Search("dc=pen,dc=local", "(objectClass=domainDNS)");
Expected behavior
A result coming back - not an error complaining about the missing bind.
Desktop (please complete the following information):
OS: macOS Monterey, apple silicon
LdapForNet 2.7.15
.NET 6.0.301
Openldap version 2.6.2
LDAP server Active Directory
Additional context
I'll take the tldr first;
Looking at the same query using the ldapsearch command line utility I notice that the ldap4net library after receiving the search result (the searchResEntry packet) does a lot of dns lookups and then an additional bind (to root?) before it receives a searchResDone with the error. The library sends out 6 messages where as the command line is done after the searchResEntry packet with messageId 2.
Windows works as expected albeit I have not looked at the network layer to compare it to the macos version.
Some details on what I see on the wire:
The commandline I used to compare the network traffic
Describe the bug
After a successful bind, a search throws the Operations error. 000004DC: LdapErr: DSID-0C090A5C, comment: In order to perform this operation a successful bind must be completed on the connection.
To Reproduce
Any search on my particular setup would do. E.g
Expected behavior
A result coming back - not an error complaining about the missing bind.
Desktop (please complete the following information):
Additional context
I'll take the tldr first;
Looking at the same query using the ldapsearch command line utility I notice that the ldap4net library after receiving the search result (the searchResEntry packet) does a lot of dns lookups and then an additional bind (to root?) before it receives a searchResDone with the error. The library sends out 6 messages where as the command line is done after the searchResEntry packet with messageId 2.
Windows works as expected albeit I have not looked at the network layer to compare it to the macos version.
Some details on what I see on the wire:
The commandline I used to compare the network traffic
The initial response for the search (the searchResEntry packet) is exactly the same between the two implementations (commandline and ldapfornet).
The sequence for ldap4net is:
bindResponse(1)
searchResEntry(2)
bindResponse(6)
searchResDone(5)
Note that I don't see messageID 3 or 4 and 5 is coming after we have received 6.
The text was updated successfully, but these errors were encountered: