Bug 44034 – Document best practice for custom (translated) user and group names (with well known SIDs)

Bug 44034 - Document best practice for custom (translated) user and group names (with well known SIDs)


Summary:	Document best practice for custom (translated) user and group names (with wel...

Status:	RESOLVED WONTFIX

Product:	UCS extended documentation
Classification:	Unclassified
Component:	Developer documentation
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Docu maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2017-03-22 19:45 CET by Arvid Requate
Modified:	2024-04-17 13:16 CEST (History)
CC List:	1 user (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?:	Yes
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2017032121000563
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Arvid Requate

2017-03-22 19:45:06 CET

The developer guide should document best practice for custom (translated) user and group names (with well known SIDs):


## In Python or UCR templates:
@!@
from univention.lib.misc import custom_username, custom_groupname
groups_default_domainadmins = custom_groupname('Domain Admins')
@!@


## And in Shell:
. /usr/share/univention-lib/base.sh
groups_default_domainadmins=$(custom_groupname "Domain Admins")

Comment 1 Nico Gulden

2024-04-17 13:16:13 CEST

This bug hasn't seen any update for several years. I close it.

If you still see a need for it, you can reopen the bug. Please add an argumentation about why it's important to take care of it.