Unable to access ldaps - ldapjs error about passport-ldapauth HOT 10 CLOSED

I should also note that I am using the npm install passport-ldapauth, so I am using the current version. I noticed in your ldapauth-fork that you had tried to correct this issue.

from passport-ldapauth.

This issue comes from ldapjs/node-ldapjs#256, encrypted connections work fine with Node.js v0.10 (I told this to mr. Carpani in response to his email but he did not include the reason to the reply in the question above).

I'm going to see if new version of ldapjs will be released soonish, I prefer not to depend on unreleased versions (one reason being that I know the library is used in environments that have restricted Internet access and installing from GitHub would not work).

from passport-ldapauth.

Ah I see. I appreciate such a quick reply back! I suppose I just got really confused when the version was first: [email protected] and then after I apply that pull, it's still that same version. Furthermore, several of the sub-modules have pretty old versions it appears ex: [email protected] -> [email protected].

Appreciate the quick response!

from passport-ldapauth.

Yeah, the versions come from ldapjs package.json when you install from GitHub, so it might seem confusing. In reality there has been quite a lot of changes since the release of [email protected], including eg. bunyan dependency upgrade.

But good news is that you should be able to work around this. If you add ldapjs (from GitHub) to the package.json of your project, ldapauth-fork and therefore passport-ldapauth should use that one instead, ie:

{
  ...
  "dependencies": {
    "ldapjs": "mcavage/node-ldapjs",
    "passport-ldapauth": "0.3.0",
    ...
  }
}

from passport-ldapauth.

Thanks for the suggestion on adding mcavage/node-ldapjs as a dep. You might want to consider doing that in passport-ldapauth's package.json too, since the author of node-ldapjs doesn't seem too eager to fix things there (looking at the last comments being 17 days old, the patch more than a month now).

from passport-ldapauth.

As I told in ldapjs/node-ldapjs#258, we can bypass the dtracer exceptions, since it is an optional module.

npm install passport-ldapauth --no-optional

from passport-ldapauth.

Thank you a lot for the workaround! With this is works...

from passport-ldapauth.

Any chance of a newer version ( with this fix) being released soon...can't depend on an unreleased version.

from passport-ldapauth.

@mayur-arora well there has not been a new release of ldapjs so me adding this unreleased dependency to this module kinda makes you use an unreleased version as well :) And I too don't want to publish a module that depends on an unreleased version, but if someone wants to work around this issue by using the unreleased version of ldapjs it is entirely possible as described above.

from passport-ldapauth.

@vesse Thanks . Just want to confirm. I was actually referring to the fix for ldapjs/node-ldapjs#256

from passport-ldapauth.