Bug 31273 - Standard AD groups created with arbitrary SIDs
Standard AD groups created with arbitrary SIDs
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: S4 Connector
UCS 3.1
Other Linux
: P5 normal (vote)
: ---
Assigned To: Connector maintainers
http://support.microsoft.com/kb/24333...
:
Depends on: 29486
Blocks:
  Show dependency treegraph
 
Reported: 2013-05-02 18:27 CEST by Arvid Requate
Modified: 2017-08-08 07:09 CEST (History)
1 user (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?: 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.034
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 2013-05-02 18:27:49 CEST
Currently some of the "well-known" security accounts are created in the join script of the S4 Connector, but with arbitrary SIDs, which get synchronized into the Samba/Active Directory, e.g.:

dn: CN=Group Policy Creator Owners,CN=Groups,DC=school30u1,DC=qa
objectSid: S-1-5-21-2279818299-2170836941-2993483381-11105

This group e.g. should have RID 520 (see URL)
The following group SIDs should be fixed:

* "Group Policy Creator Owners"
* "RAS and IAS Servers"
* "Domain Computers"
* "Cert Publishers"
* "Schema Admins"
* "Enterprise Admins"
* "Enterprise Read-only Domain Controllers"
* "Denied RODC Password Replication Group"
* "Allowed RODC Password Replication Group"
Comment 1 Stefan Gohmann univentionstaff 2013-05-06 07:44:13 CEST
Bug #29486 needs to be fixed for this issue.
Comment 2 Stefan Gohmann univentionstaff 2017-06-16 20:40:28 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 3 Stefan Gohmann univentionstaff 2017-08-08 07:09:53 CEST
This issue has been filed against UCS 3.1.

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

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