ldap

Calling client.search(base,opts, function(err, res){}) with a malformed filter (e.g. (uid=)) means you can't clean up the client connection without triggering an error as the outstanding search message's error callback is triggered.

When client.ubind() called there is still a message on the queue. Has the search not returned an err then I could have used the messageID with `client.aba

From @benyanke on April 19, 2018 1:14

Added a bunch of optional config options in #8 , however, didn't also update the example config file to show off these cases.

Copied from original issue: nmcclain/glauth#12