LDAP on windows not working

[JohanDonne]

I did this

 >curl "ldap://ldap.forumsys.com"
 curl: (62) LDAP local: No Memory

I expected the following

 curl "ldap://ldap.forumsys.com"
 DN:
         objectClass: top
         objectClass: OpenLDAProotDSE

curl/libcurl version

curl 7.65.3 (x86_64-pc-win32) libcurl/7.65.3 OpenSSL/1.1.1c (Schannel) zlib/1.2.11 brotli/1.0.7 WinIDN libssh2/1.9.0 nghttp2/1.39.2
Release-Date: 2019-07-19

operating system

Both Windows 10 and Windows Server 2016

[bagder]

Any chance you can single-step through the code and see what function call that acts up?

[JohanDonne]

I will try, but I'm pretty busy right now and I need to find the time to setup the environment to do so...

[jay]

bisected to f0fe66f @snikulov , original error:
curl: (38) LDAP local: bind via ldap_win_bind Invalid DN Syntax
error changed to "no memory" after 1b443a7 @samsinsane

[samsinsane]

My apologies, I can see the issue is that it's valid for conn->data->state.up.query to be NULL, but at the time I assumed that query being NULL meant that there was a memory allocation failure. I think that this condition needs to also check if conn->data->state.up.query is not NULL and everything should just work? I won't have time to make this change and test it out for awhile, so someone else might need to do this.

[jay]

A partial fix for this issue has landed in 8bb3a95, which addresses the erroneous out of memory error. Now the error message is:

curl: (38) LDAP local: bind via ldap_win_bind Invalid Credentials

[jeroen]

This problem has also been reported in the R bindings. This image can be used to reproduce:

docker run --privileged -d -p 389:389 rroemhild/test-openldap

And then:

curl "ldap://localhost:389"
# Error: LDAP local: No Memory