James Sumners

What is the action you are expecting with creating this issue? How does this relate to the `ldapjs` source code?

Would you like to submit a pull request to solve this issue?

You should attempt the bind _after_ the search has completed, not upon receiving the first entry. After the search has ended, you should have an array of search results. If...

It's possible. I will say I use the server part extensively in https://github.com/jsumners/node-activedirectory for unit testing. But for the moment I am much more concerned with getting a new `ldapjs`...

If you'd like to send a pull request to add this feature, we would certainly consider it. Remember to add unit tests.

What you are showing is that you have an instance of `EntryAlreadyExistsError`. That means you should be able to `console.log(err.code)` and see `68`. Is this not the case?

Redacted trace logs would be very helpful.

`client.starttls` would be something you perform immediately after creating the client and before performing any other operations. So at the least, this could use some better documentation. A PR would...

No. That's not how LDAP works. However, there is a server extension that may help. See the PR released under `ldapjs@next` -- https://github.com/ldapjs/node-ldapjs/pull/553

@saostad if you are willing to pick up the PR, please include the original work by following these instructions -- https://gist.github.com/jsumners/461ef7a64545108635cc437fde112721