Bug 45053 - Users with primaryGroup should not be able to be removed from this Group
Users with primaryGroup should not be able to be removed from this Group
Status: CLOSED DUPLICATE of bug 45052
Product: UCS
Classification: Unclassified
Component: UMC - Groups
UCS 4.1
Other Linux
: P5 normal (vote)
: UCS 4.1-x-errata
Assigned To: UMC maintainers
UMC maintainers
:
Depends on: 45052
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-21 15:03 CEST by Nico Stöckigt
Modified: 2017-07-21 15:30 CEST (History)
2 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 3: Simply Wrong: The implementation doesn't match the docu
Who will be affected by this bug?: 5: Will affect all installed domains
How will those affected feel about the bug?: 2: A Pain – users won’t like this once they notice it
User Pain: 0.171
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2017071221000724
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 Nico Stöckigt univentionstaff 2017-07-21 15:03:46 CEST
+++ This bug was initially created as a clone of Bug #45052 +++

A user 'userA' with primaryGroup 'GroupX' is _allways_ member of this group. In openLDAP 'userA' is also added to this group via 'memberUid' and 'uniqueMember'. When you remove 'userA' from 'groupX' the primaryGroup of 'userA' is not touched - he still has primaryGroup 'groupX' and due to that is effectively member of this group. It seems to doesn't make sense to be able to remove the mapping of an user from it's primaryGroup. At least in UMC the user should be grayed out and not removeable.
Comment 1 Florian Best univentionstaff 2017-07-21 15:30:37 CEST

*** This bug has been marked as a duplicate of bug 45052 ***
Comment 2 Florian Best univentionstaff 2017-07-21 15:30:56 CEST
Will be reopened when we decide to make a backport.