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

Add one more error code which is LDAP_PARTIAL_RESULTS: 9 #367

Closed
wants to merge 1 commit into from

Conversation

gaupoit
Copy link

@gaupoit gaupoit commented Apr 4, 2016

Related to this issue: #366

Copy link
Member

@jsumners jsumners left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Error code 9 seems to be a reserved error code -- https://tools.ietf.org/html/rfc4511#section-4.1.9

Can you point me to the server implementation you use that i returning this code? Is it OpenLDAP, a commercial implementation, or your own implementation?

@frostie614
Copy link

I have been doing a quick search for information related to this and have found the following:

Microsoft
LdapWiki
IBM

Is this of any use?

1 similar comment
@frostie614
Copy link

I have been doing a quick search for information related to this and have found the following:

Microsoft
LdapWiki
IBM

Is this of any use?

@jsumners
Copy link
Member

@frostie614 yep. That answers it.

A follow-up PR that adds a working integration test would be ideal, but I have no idea how to force it.

@jsumners jsumners changed the base branch from master to next January 16, 2020 13:56
@jsumners jsumners added the closed-for-v2 Issues that were closed at the release of v2.0.0 but may still need to be addressed. label May 31, 2020
@jsumners jsumners closed this May 31, 2020
@jsumners
Copy link
Member

⚠️ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.

Please include a minimal reproducible example
when opening a new issue.

@ldapjs ldapjs locked as resolved and limited conversation to collaborators Mar 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
closed-for-v2 Issues that were closed at the release of v2.0.0 but may still need to be addressed.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants