Bug 27574 - check for collisions of user and group names
check for collisions of user and group names
Status: RESOLVED DUPLICATE of bug 26289
Product: UCS
Classification: Unclassified
Component: UDM (Generic)
UCS 3.0
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2012-06-14 10:09 CEST by Arvid Requate
Modified: 2018-04-13 13:28 CEST (History)
2 users (show)

See Also:
What kind of report is it?: ---
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Arvid Requate univentionstaff 2012-06-14 10:09:48 CEST
Überschneidungen zwischen Benutzernamen und Gruppennamen bereiten sowohl Samba3 Probleme als auch im S4-Connector, wo sie Rejects verursachen. Über eine per UCR konfigurierbare Eindeutigkeitsprüfung auf Namen in UDM Modulen users und groups sollten sich solche Kollisionen zwischen Benutzer- und Gruppennamen vermeiden lassen.
Comment 1 Arvid Requate univentionstaff 2014-03-11 15:18:01 CET
Creating users and groups with identical names causes collisions in the S4 Connector and in the AD Connector and may cause problems in Samba3 as well. IMHO a check should be implemented in the Univention Directory Manager modules users/user and groups/group to avoid these conflicts. If necessary, the check may be disabled via UCR.

This happened again in a customer environment causing rejects in the AD Connector.
Comment 2 Stefan Gohmann univentionstaff 2014-03-11 15:21:43 CET
Duplicate of Bug #26289?
Comment 3 Florian Best univentionstaff 2016-09-24 16:00:43 CEST
(In reply to Stefan Gohmann from comment #2)
> Duplicate of Bug #26289?
Yes. And also the check meanwhile exists for gidNumber/uidNumber, too.

*** This bug has been marked as a duplicate of bug 26289 ***