Skip to content

Conversation

@ccanoness
Copy link

cause: when modify with lost connection make an app crash
maybe merge to original v3.x.x can solve this

jeremycx and others added 27 commits November 17, 2015 14:26
Prior versions of `findandbind()` passed `(err, data)` to the callback.
This functionality was broken, I believe inadvertently, in commit
a4b9ce6 It's still documented in
the README and the callbacks in the unit tests still accept
`(err, data)`. Since it was broken in a minor version bump (3.0->3.1),
it will break existing code that relies on `data` being passed back
and uses the caret operator to specify dependency versions.

Restore that functionality, by passing the found entry
to the callback supplied to `findandbind()`.
findandbind: pass found entry to callback
The function that gets called when a connection is established comes from
the `connect` option (see [here](https://github.com/jeremycx/node-LDAP/blob/master/index.js#L78)
and [here](https://github.com/jeremycx/node-LDAP/blob/master/index.js#L104)).
It was documented as the `reconnect` option.

Fix the documentation to match the code.
README.md: fix name of onconnection function in docs
restore support for paging
Only tested with PLAIN and GSSAPI support on Linux.
Requires Cyrus SASL installed at /usr/include/sasl/sasl.h.

GSSAPI support tested with AD and LDS.
PLAIN tested with OpenLDAP.
Add SASL bind support.
SASL GSSAPI bind was not being completed.
Removing Dependence on lodash
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants