Bug 34226 - S4-Connector: GPO DS-ACL replication
S4-Connector: GPO DS-ACL replication
Status: RESOLVED WONTFIX
Product: UCS@school
Classification: Unclassified
Component: Samba 4
UCS@school 3.2 R2
Other Linux
: P5 normal (vote)
: UCS@school 3.2.x
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-03-03 14:00 CET by Arvid Requate
Modified: 2019-02-05 21:26 CET (History)
2 users (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?:
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 2014-03-03 14:00:28 CET
Currently the S4-Connector does not replicate the nTSecurityDescriptor of the GPO objects to OpenLDAP and back. In multi-school domains this may lead to inconsistencies between the NTACLs in the sysvol share and the nTSecurityDescriptor in the Samba/ADDS, which may cause irritating warnings to pop up at an Administrator using the Microsoft Group Policy Management Console.

We should extend the UCS OpenLDAP msgpo schema to support this attribute and extend the S4 Connector to synchronize it. Maybe it's best to replicate this as a blob rather than as a SDDL string representation.
Comment 1 Sönke Schwardt-Krummrich univentionstaff 2014-03-03 15:52:54 CET
Already noticed by one larger UCS@school customer. Not the "irritating warnings" by itself but the missing sync of the corresponding attributes.
Comment 2 Florian Best univentionstaff 2017-06-28 14:56:43 CEST
There is a Customer ID set so I set the flag "School Customer affected".
Comment 3 Sönke Schwardt-Krummrich univentionstaff 2019-02-05 21:26:41 CET
This issue has been filled against UCS@school 3.2. The maintenance with
bug and security fixes for UCS@school 3.2 has ended on Dec 31, 2016.

Customers still on UCS 3.x are encouraged to update to UCS 4.3 (or later). 
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.