Bug 42449 - User Template: Primary Group default value - Allow creation of custom primary group
User Template: Primary Group default value - Allow creation of custom primary...
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: UMC - Users
UCS 4.1
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: UMC maintainers
:
Depends on: 42335
Blocks:
  Show dependency treegraph
 
Reported: 2016-09-20 15:37 CEST by Daniel Orrego
Modified: 2019-01-03 07:23 CET (History)
4 users (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.011
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 Daniel Orrego univentionstaff 2016-09-20 15:37:33 CEST
When creating a user via a template, an option to create a custom group could be offered (when setting primaryGroup and groups). Currently one can only select the primary group from the list of existing groups.

If it makes sense, one could, for instance, specify something like primaryGroup:<username> in the template to create one group per user (Like with useradd, where a group with the same name as the username is created if no group name is specified)

+++ This bug was initially created as a clone of Bug #42335 +++
Bug 42335 asks that 'Domain Users' be the default primary group if no group is explicitly selected (to fix UMC choosing the first in the list).
Comment 1 Alexander Kläser univentionstaff 2016-10-05 14:34:52 CEST
Could an extended attribute do the trick? See also Bug 37710 as an example for the field username.
Comment 2 Stefan Gohmann univentionstaff 2019-01-03 07:23:22 CET
This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.