mirror of
https://github.com/lldap/lldap.git
synced 2026-04-26 00:36:01 +03:00
[GH-ISSUE #1164] [BUG] Changing the Display Name of a group changes also its CN #415
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#415
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 @Wrong-Code on GitHub (May 1, 2025).
Original GitHub issue: https://github.com/lldap/lldap/issues/1164
Describe the bug
Changing the Display Name attribute of a group has a side effect to also rename the group (altering its CN) to the same value.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
CN and displayName are two different attributes. They are managed correctly for users, but not for groups.
Logs
None.
Additional context
None.
@nitnelave commented on GitHub (May 1, 2025):
Actually, in LLDAP they are aliases of each other for groups.
You can create your own custom attribute (e.g. "name") and add a different name for each group, mapping it differently in the various services.
This is intended for simplicity, the use case of groups being a user-facing entity being considered rarer than not, so having a single name/CN for groups simplifies administration.
@Wrong-Code commented on GitHub (May 1, 2025):
If so, I would suggest to remove the display name from groups. As it is its usage is misleading, being displayName is a well-defined attribute in many LDAP implementations, and it's not expected to be the same thing of the common name.
@nitnelave commented on GitHub (May 1, 2025):
I know that I'm departing from convention; but LLDAP does not aim to be a conventional LDAP server, and it is aimed primarily at people who are not very familiar with LDAP or other LDAP servers.
I feel like this is a good default situation, though it could be more clearly communicated. Thankfully, we have ongoing work to clarify the attributes and more specifically the aliases, so it will be clearer that display name, cn and uid are the same thing for groups.