ldap

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

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

Is your feature request related to a problem? Please describe.

I'm trying to reset the password as part of doing some automation, and the CLI's outputting both logs and the password output to stderr, which makes that harder.

Describe the solution you'd like

Ideally, an option to return the password/message as a JSON object like this (but on a single line):

kanidmd rec