-
Notifications
You must be signed in to change notification settings - Fork 448
socket.socket undefined using TLS on Node 0.12.7 #289
Comments
Using latest dev version ( |
Yes, I have this issue with any of the node 0.12.x builds. okay for 0.10.36 |
Hi @mcavage, have you got an ETA to cut new release out of master and push to npm? This issue blocking us a bit as we switched to 0.12. |
0.8.0 is mostly ready, save for updated documentation. |
How were you able to install this on node 0.12. As per Issue #281, didn't think this could be installed...? |
I just put |
Hi @pfmooney . Thanks for working on this project! |
I'm working on finishing updates to the documentation. |
1.0.0 has been released with updated dependencies |
I get below error Invalid data, chunk must be a string or buffer, not object |
Please include a minimal reproducible example |
When trying to connect using
ldapjs.createClient({url: 'ldaps://url.to.ldap.tld:636/'})
, I'm getting this stack on Node 0.12.7:The code there is:
opts.secure
equals totrue
butsocket.socket
doesn't exist (isundefined
).Moreover, looking at the Nodejs
tls.connect()
API, I don't understand why a distinction is done between secured (usingtls
API, and callingsocket.socket
) and unsecured (usingnet
API and calling directlysocket
) connections.I'm using node-ldapjs v0.7.1.
The text was updated successfully, but these errors were encountered: