mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #255] ldapsearch query does not respect scope #93
Labels
No labels
backend
blocked
bug
cleanup
dependencies
docker
documentation
duplicate
enhancement
enhancement
frontend
github_actions
good first issue
help wanted
help wanted
integration
invalid
ldap
pull-request
question
rust
rust
tests
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/lldap-lldap#93
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ikaruswill on GitHub (Jul 14, 2022).
Original GitHub issue: https://github.com/lldap/lldap/issues/255
Context
I was just debugging the problem described in https://github.com/nitnelave/lldap/issues/254 and I came across this one when tinkering with the search scope.
Problem
When varying scope for
ldapsearchbetweenbaseandonewe'd expect the search to be on the base object itself, and one subtree down. However, varying scope seems to have no effect when search is performed against an LLDAP server.Here I perform search for a
objectClass=personthat is amemberOfcn=adminsgroup with a search base ofou=people. I set the scope to bebaseso the search will only search the objectou=people,dc=example,dc=com, which itself is not anobjectClass=personso should return 0 results. Only if scope is set toonewill the search look at direct descendants. (Scope docs)Against LLDAP:
Against OpenLDAP (no results):
Relevant logs:
@nitnelave commented on GitHub (Jul 14, 2022):
Yeah, the logic around scope is simplified, since we don't have objects at different levels. Are you actually running into issues because of that?
@ikaruswill commented on GitHub (Jul 14, 2022):
I see. At the moment not really. Only the dn issue is causing problems with Home assistant LDAP script. Thought I'd flag it out here for awareness!