DC connection remains active on InvalidCredentialsError

Hi, I’m triyng to catch all the possible errors for my AD LDAP query. If I put an invalid or inaccessible url or basedn the library correctly calls my callback with a non-null err parameter. When I issue a bad username or password for binding, the library retries the bind another time than hangs because the connection with the DC remains active.

This is the code I’m using for my query:

var ActiveDirectory = require('activedirectory');
var ad = new ActiveDirectory({
        url: '...',
        baseDN: '...',
        username: '...',
        password: 'wrongpassword',
});
ad.find('(mobile=...)', function(err, user) {
       if(err) {
                console.log(JSON.stringify(err));

                return;
        }

        if(!user) {
                console.log('user not found');
                return;
        }

        console.log("User of ... found: " + user.users[0].displayName);

});

And this is the results (after this output node doesn’t exit like it does on the other Ldap errors):

{"dn":"","code":49,"name":"InvalidCredentialsError","message":"80090308: LdapErr: DSID-0C0903CF, comment: AcceptSecurityContext error, data 52e, v2580\u0000"}
{"dn":"","code":49,"name":"InvalidCredentialsError","message":"80090308: LdapErr: DSID-0C0903CF, comment: AcceptSecurityContext error, data 52e, v2580\u0000"}

I’ve used wtfnode to show the hanging connection:

[WTF Node?] open handles:
- Sockets:
  - undefined:undefined -> undefined:undefined
    - Listeners:
  - undefined:undefined -> undefined:undefined
    - Listeners:
  - (MY IP):57795 -> (DC IP):389

Many thanks for your work.

[pbatey]

I’ve filed a pull-request against ldapjs to address this issue: https://github.com/mcavage/node-ldapjs/pull/405

[denis-peshkov]

Guys, I have the same issue, so merge it please asap.