Bug 42523 – Don't sync incomplete objects back from AD

Bug 42523 - Don't sync incomplete objects back from AD


Summary:	Don't sync incomplete objects back from AD

Status:	REOPENED

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

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-09-28 06:36 CEST by Stefan Gohmann
Modified:	2020-03-16 10:17 CET (History)
CC List:	1 user (show)

See Also:	35391 42522
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?:	1: Will affect a very few 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.023
Enterprise Customer affected?:	Yes
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016090921000131
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 Stefan Gohmann

2016-09-28 06:36:00 CEST

If a user is created in UCS the synchronization to AD is done in multiple steps. This is required because it is not allowed to create the user with all attributes in one step.

If one step fails, the user is not locked and the object is synchronized back. We changed it in the S4 Connector already: Bug #35391.

See also Bug #42522 and Ticket #2016090921000131.

Comment 1 Stefan Gohmann

2019-01-03 07:19:25 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 are encouraged to update to UCS 4.3. 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.

Comment 2 Julia Bremer

2020-03-16 10:17:16 CET

This issue is the reason why 52_s4connector.134sync_incomplete_attribute_ucs.master237 
fails in our jenkins job s4connector-w2k8r2-german
environment where both S4-Connector and AD-Connector are installed.