Bug 42524

Summary:	Meta Bug for the merge of S4 Connector changes to the AD Connector
Product:	UCS	Reporter:	Stefan Gohmann <gohmann>
Component:	AD Connector	Assignee:	Samba maintainers <samba-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	best, michelsmidt, oyen
Version:	UCS 4.1
Target Milestone:	---
Hardware:	Other
OS:	Linux
What kind of report is it?:	Development Internal	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:
Bug Depends on:	36480, 18501, 24923, 27452, 29988, 35527, 40813, 41335, 42525, 42618
Bug Blocks:

Description Stefan Gohmann

2016-09-28 07:41:07 CEST

We have implemented several improvements in our S4 Connector code. We didn't change the AD Connector in the same way.

For example:
 Bug 33621 - Concurrent changes in S4 and OpenLDAP 
 Bug 35391 - Failed first sync may result in attribute deletion
 Bug 32263 - sync ucs to s4 should skipp creation of objects missing in UDM

I think we should check the changes and merge them.

The alternative is to make one base package but I think we should start with the code merge first.

Comment 1 Stefan Gohmann

2016-09-28 07:57:09 CEST

Another example:
 Bug 28910 - group und user mapping tables für S4 Connector mapping

Comment 2 Stefan Gohmann

2016-09-28 08:31:42 CEST

Bug 36317 - S4 connector removes shadowMax and shadowLastChange on password change via samba/kerberos

Comment 3 Stefan Gohmann

2016-09-28 09:38:24 CEST

Bug 31172 - sync from ucs: 'otherTelephone': no such attribute for delete

Comment 4 Stefan Gohmann

2019-01-03 07:20:18 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.