mirror of
https://github.com/lldap/lldap.git
synced 2026-04-25 08:15:52 +03:00
[GH-ISSUE #468] When query user memberof attribute maybe wrong group dn is returned #177
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#177
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 @zozzz on GitHub (Mar 3, 2023).
Original GitHub issue: https://github.com/lldap/lldap/issues/468
In this line the group common name returned as uid, but the documentation says the group name is
cn=family,ou=groups,dc=example,dc=com. The memberOf queries is working like this naming convention.@nitnelave commented on GitHub (Mar 4, 2023):
Both are valid. Technically, uid is probably more future proof, but it doesn't really matter.
@zozzz commented on GitHub (Mar 4, 2023):
Can you rename it to cn? I want to use with OPNSense, and excepting cn instead of uid. I think this is more standard in group names. Maybe this change breaks other apps.
@martadinata666 commented on GitHub (Mar 4, 2023):
you can override
User naming attributetouid, if that is what you mean by acceptingcn@nitnelave commented on GitHub (Mar 4, 2023):
That would more be a request for opnsense, to add support for uid. It's
perfectly standard.
On Sat, 4 Mar 2023, 10:22 Vetési Zoltán, @.***> wrote:
@zozzz commented on GitHub (Mar 7, 2023):
@martadinata666 Not the user name is my problem.
@nitnelave Ok. I just think this is a bug, but just inconsistent dn naming with
(objectClass=groupOfNames).But, maybe is a good idea to use same dn everywhere.
@nitnelave commented on GitHub (Mar 7, 2023):
Alright, phrased like that it's totally fair :)