Bug 48988 – Use LDAP Post Read Control for all writes in sync_to_ucs

Bug 48988 - Use LDAP Post Read Control for all writes in sync_to_ucs


Summary:	Use LDAP Post Read Control for all writes in sync_to_ucs

Status:	REOPENED

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.4
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2019-03-14 10:23 CET by Arvid Requate
Modified:	2021-09-16 15:52 CEST (History)
CC List:	4 users (show)

See Also:	33621
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	3: Will affect average number of installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.069
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
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

2019-03-14 10:23:29 CET

For Bug #43628 we extended UDM to support the passing of the LDAP Post Read Control to allow the modifier to see the value of e.g. entryCSN directly after the modification. We should use that in the S4-Connector for all writes to OpenLDAP. Currently it's only used for the NTSecurityDescriptor.

The benefit of this is, that we reduce the ping-pong of changes when a change originates from Samba/AD. With the control, the S4-Connector can identify which changes reported from the Listener are simply hist own and can be ignored.

Unfortunately AD (and Samba) currenlty don't support that control as yet, so the effect of this is probably not a massive percentage in speedup. But it makes a massive difference for staccato-like changes from the Samba side: We had reports of Admins changing user names, mistyping, and fixing in typical human interaction speed -- and then the S4-Connector interferred and overwrote their changes. That would be avoided by the proposed change.

Comment 1 Florian Best

2021-03-02 21:33:50 CET

The post-read-control has been activated for all objects in Bug #52358.

*** This bug has been marked as a duplicate of bug 52358 ***

Comment 2 Julia Bremer

2021-03-16 09:38:48 CET

Verified - problem has been fixed with Bug #52358

Comment 3 Florian Best

2021-09-16 15:52:40 CEST

(In reply to Florian Best from comment #1)
> The post-read-control has been activated for all objects in Bug #52358.
> 
> *** This bug has been marked as a duplicate of bug 52358 ***

REOPEN: That was reverted.