When initializing an Attribute object, the 'vals' option field was being
loosely tested for content presence. By changing this test to a strict
comparison against undefined, Attribute object creation will be more
consistent across input values.
Fixmcavage/node-ldapjs#178
This is required when using node 0.10 and talking to a ldaps://
LDAP server with a self-signed cert. Otherwise you get:
$ ./ldapjs-search --url ldaps://ldap.example.com:636 ...
DEPTH_ZERO_SELF_SIGNED_CERT
In cases where one side of the connection is not communicated with valid
ASN.1/BER, it would be better to fire an error event rather than let the
exception bubble all the way up.
Fixmcavage/node-ldapjs#142
It appears that in node.js (at least recent versions), the 'close' event
is not emitted by TLS sockets. The CleartextStream class specifies that
the 'close' event is optional, so such operation is allowed. In order
to compensate, the event can be trapped at the raw net.socket instead.
Fixmcavage/node-ldapjs#161
Buffertools 2.0.1 is required to build on VC2013.
With the change to v2.x, the buffertools.extend() method must be called
to mimic the prototype extention behavior of the 1.x versions.
Fixmcavage/node-ldapjs#163
Client actions utilizing an EventEmitter may generate unhandled errors,
especially during initial connection. Tracking whether the emitter has
been sent via callback is critical for proper routing of such errors.
Fixmcavage/node-ldapjs#144
- Add 'spaced' function to DN objects allowing toggle of inter-RDN when
rendering to a string. ('dc=test,dc=tld' vs 'dc=test, dc=tld')
- Detect RDN spacing when parsing DN.
Fixesmcavage/node-ldapjs#138: user can't bind with inmemory example
In addition to fixing the userPassword authentication code, the
authorize function has been changed so any user may search after a
successful bind.
When using node 0.10, test initiation will fail due to differences in
the array.map function. This discrepancy is corrected in tap v0.4.1.
See: https://github.com/isaacs/node-tap/issues/70