Bug 36387 - Support wildcards in connector ignorelist
Support wildcards in connector ignorelist
Status: RESOLVED WONTFIX
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.2
Other Linux
: P5 enhancement (vote)
: ---
Assigned To: Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-11-03 11:40 CET by Michael Grandjean
Modified: 2020-07-03 20:54 CEST (History)
3 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?: 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?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2014103021000207
Bug group (optional): External feedback, Roadmap discussion (moved)
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Grandjean univentionstaff 2014-11-03 11:40:09 CET
Currently it's not possible to use wildcards such as '*' in 

> connector/ad/mapping/{user,group,container,ou}/ignorelist

This limits the possibilities to blacklist certain name schemata and should therefore be supported.
Comment 1 Michael Grandjean univentionstaff 2014-11-03 11:42:22 CET
See also Ticket#2014103021000207
Comment 2 Arvid Requate univentionstaff 2016-09-28 13:40:04 CEST
Would fixing Bug 42525 be enough?
Comment 3 Michael Grandjean univentionstaff 2016-09-28 14:37:53 CEST
(In reply to Arvid Requate from comment #2)
> Would fixing Bug 42525 be enough?

As far as I understand Bug 42525, no it's not enough. The idea of this Bug is to be able to do something like this:

ucr set connector/ad/mapping/user/ignorelist='nosync-*'

assuming that this would stop the follwing users from being synchronized:

nosync-michael
nosync-arvid
nosync-mary
Comment 4 Stefan Gohmann univentionstaff 2017-06-16 20:40:18 CEST
This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.
Comment 5 Ingo Steuwer univentionstaff 2020-07-03 20:54:42 CEST
This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or reopen it and update the UCS version. In this case please provide detailed information on how this issue is affecting you.