Bug 35555 - Some Well Known SIDs are missing from univention-lib/python/s4.py
Summary: Some Well Known SIDs are missing from univention-lib/python/s4.py
Status: RESOLVED WONTFIX
Alias: None
Product: UCS
Classification: Unclassified
Component: univention-lib
Version: UCS 4.4
Hardware: Other Linux
: P5 normal
Target Milestone: ---
Assignee: UCS maintainers
QA Contact:
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-08-04 14:41 CEST by Arvid Requate
Modified: 2025-02-05 09:29 CET (History)
2 users (show)

See Also:
What kind of report is it?: Release Management
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):
Customer ID:
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 univentionstaff 2014-08-04 14:41:04 CEST 
Groups like "Remote Interactive Logon" which are created in the joinscript 96univention-samba4.inst are missing from univention-lib/python/s4.py. Maybe we should add them for completeness. If we do that we need to check for changes of behaviour in the adtakeover module.
Comment 1 Stefan Gohmann univentionstaff 2017-06-16 20:38:12 CEST 
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 2 Jan-Luca Kiok univentionstaff 2025-02-05 09:29:07 CET 
This issue has been filed against UCS 4.4.

UCS 4.4 is out of maintenance and components may have vastly changed in later releases. Thus, this issue is now being closed.

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