You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 4, 2022. It is now read-only.
The SearchRequestHandler returns ResultCodeEnum.NoSuchObject whenever the search yields 0 results.
But, is that correct? I'd say yes if the path is invalid (e.g. doesn't exist), but when there's 0 results because the search term was too restrictive, a success result is more appropriate.
I've only ever been a consumer of LDAP servers, but I generally only get a 'no such object' error when I specify an invalid path. When a search yields 0 results, I get a success result with 0 results instead.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
SearchRequestHandler
returnsResultCodeEnum.NoSuchObject
whenever the search yields 0 results.But, is that correct? I'd say yes if the path is invalid (e.g. doesn't exist), but when there's 0 results because the search term was too restrictive, a success result is more appropriate.
I've only ever been a consumer of LDAP servers, but I generally only get a 'no such object' error when I specify an invalid path. When a search yields 0 results, I get a success result with 0 results instead.
The text was updated successfully, but these errors were encountered: