Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SASL external with TLS client certs
See original GitHub issueI added a similar request/question to ldapjs but thought I’d ask here as well, since this seems better maintained. I’ve read the issues and docs and am pretty sure this is not supported, but wanted to check anyway.
I need to use LDAP (as a client) over ldaps:// where the tlsOptions contain a key and cert for TLS client authentication. I.e. the LDAP server (the peer) will verify my LDAP client via TLS client authentication.
But I want this TLS client auth to be used with the “SASL EXTERNAL mechanism” (page 29 in https://docs.ldap.com/specs/rfc4422.txt).
As far as I can understand, this is something I can currently achieve with ldapsearch by supplying the -Y EXTERNAL.
So with all that in mind, since ldapts already supports TLS using client cert/key, is it possible for it to use -Y EXTERNAL so that they are also used as the SASL mechanism “EXTERNAL”?
Issue Analytics
- State:
- Created 3 years ago
- Comments:44 (44 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Thank you for the additional info, I’m hoping it helps me wrap my head around sasl! It seems that ldapi (ldap over unix sockets) is somewhat related. I wasn’t planning on supporting that - do you know if it’s needed from your setup? I’ll try to get back to looking into this later this week or next.
btw, you shouldn’t need to @ mention me anymore. I think I resolved my notification issues
Just installed the package from npm and ran the app. Still working for my ldaps request