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
exop sample (whois) not working #370
Comments
ptusch
changed the title
exop sample (whoami) not working
exop sample (whois) not working
Apr 28, 2016
jsumners
added
the
potential-ci-test
Issues that may need a CI test against an OpenLDAP server
label
Aug 26, 2019
jsumners
removed
the
potential-ci-test
Issues that may need a CI test against an OpenLDAP server
label
Nov 16, 2019
jsumners
added a commit
that referenced
this issue
Nov 16, 2019
This issue should be resolved in |
Please include a minimal reproducible example |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
the
exop
sample on ldapjs.org does not work with OpenLDAP (2.4.40).It seems to be that ldapjs doesn't fully respect RFC 4532.
Point 2.1. of the RFC:
Here's my output for exop with the OID
1.3.6.1.4.1.4203.1.11.3
Removing L589 of the client.js, results is a nice WhoIs output.
This is my sample to call the exop with the who is OID:
The problem is that
requestValue
is encoded into Ber and then send to LDAP.I'm not sure how to solve the issue without much trouble. I don't know all OID and their RFC so I assume having a list of OID which need to be treated special is needed.
Simply removing the key
requestValue
when the content isnull
sounds like trouble.Any thoughts on this and how you'd like it to be solved? I'd totally PR you with a fix.
Some additional data about my versions:
node: 4.3.3
ldapjs: 1.0.0
The text was updated successfully, but these errors were encountered: