Bug 49314 - connector/ad/mapping/ou/ignorelist is not working
connector/ad/mapping/ou/ignorelist is not working
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.3
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on: 20517
Blocks:
  Show dependency treegraph
 
Reported: 2019-04-17 16:48 CEST by Nico Stöckigt
Modified: 2019-04-17 19:13 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 5: Major Usability: Impairs usability in key scenarios
Who will be affected by this bug?: 2: Will only affect a few installed domains
How will those affected feel about the bug?: 5: Blocking further progress on the daily work
User Pain: 0.286
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2019041621000541
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 Nico Stöckigt univentionstaff 2019-04-17 16:48:24 CEST
In a customers environment it seems that the ou/ignorelist is not working. Values in that UCR-V are parsed into the mapping.py but seem to have no effect.

Current Version is latest UCS 4.3-4
Comment 1 Arvid Requate univentionstaff 2019-04-17 19:13:45 CEST
See Bug 20517#c5, the UCRV would ignore the ou-object itself, but not the subtree. If the OU exists on both sides, the AD-Connector probably synchronizes the objects within. So in itself, that UCRV doesn't help much. One would probably want to have the behavior of global ignore subtree. We have Bug 47008 to make that configurable via UCR.