Bug 51773 – AD-Connector doesn't support synchronizing users/groups to different target container

Bug 51773 - AD-Connector doesn't support synchronizing users/groups to different target container


Summary:	AD-Connector doesn't support synchronizing users/groups to different target c...

Status:	NEW

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

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

URL:
Keywords:

Depends on:	5407
Blocks:
	Show dependency tree / graph

Reported:	2020-08-05 13:59 CEST by Arvid Requate
Modified:	2020-08-05 14:00 CEST (History)
CC List:	4 users (show)

See Also:
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?:	2: Will only affect a 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.046
Enterprise Customer affected?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2011012710001863, 2012050221003477, 2013071821000855, 2015050521000558, 2020072821000322
Bug group (optional):
Max CVSS v3 score:

Flags:	requate: Patch_Available+

Attachments
apply-con_default_dn.patch (1.23 KB, patch) 2020-08-05 13:59 CEST, Arvid Requate	Details \| Diff
View All 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

2020-08-05 13:59:01 CEST

The AD-Connector doesn't support synchronizing users/groups to a different target container. The mapping parameters con_default_dn and ucs_default_dn are not considered.


+++ This bug was initially created as a clone of Bug #5407 +++

Comment 1 Arvid Requate

2020-08-05 13:59:32 CEST

Created attachment 10449 [details]
apply-con_default_dn.patch

Created attachment 10448 [details]
apply-con_default_dn.patch

The attached patch would fix it.

Alternatively the "position_mapping" could be added, e.g. to the 'user' property mapping file:

position_mapping=[(',cn=users,@%@ldap/base@%@', ',OU=some,OU=other,@%@connector/s4/ldap/base@%@')],