Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cert is empty error #153

Open
tomalex0 opened this issue Apr 6, 2017 · 3 comments
Open

Cert is empty error #153

tomalex0 opened this issue Apr 6, 2017 · 3 comments

Comments

@tomalex0
Copy link

tomalex0 commented Apr 6, 2017

At times while connecting to ldap we are getting below error but not always.
"reason": "Cert is empty",

Can somebody help me identifying the actual cause

@tomalex0
Copy link
Author

tomalex0 commented Apr 6, 2017

Further error trace

{ Error: Hostname/IP doesn't match certificate's altnames: "Cert is empty"
    at Object.checkServerIdentity (tls.js:199:17)
    at TLSSocket.<anonymous> (_tls_wrap.js:1091:29)
    at emitNone (events.js:86:13)
    at TLSSocket.emit (events.js:185:7)
    at TLSSocket._finishInit (_tls_wrap.js:603:8)
    at TLSWrap.ssl.onhandshakedone (_tls_wrap.js:433:38)

@tomalex0
Copy link
Author

tomalex0 commented Apr 6, 2017

I used this tool to test out same flow and it was working fine
http://www.computerperformance.co.uk/w2k3/utilities/ldp.htm#Free

@akdor1154
Copy link

akdor1154 commented May 15, 2017

I think this is seen when the cert lacks a subject name (i.e. it only has SubjectAltName). This is perfectly valid as far as I am aware however it trips up something in this node-tls-ldapjs-activedirectory stack. Looking into it (as a user, not a dev).
EDIT: this is a node bug. nodejs/node#11771
similar libraries to this are working around it themselves: auth0/ad-ldap-connector@1f4dd2b

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants