Bug 31935 – Add option to make S4 Connector not sync specific DNs

Bug 31935 - Add option to make S4 Connector not sync specific DNs


Summary:	Add option to make S4 Connector not sync specific DNs

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 3.1
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:	31600
	Show dependency tree / graph

Reported:	2013-07-09 15:54 CEST by Arvid Requate
Modified:	2017-08-08 07:09 CEST (History)
CC List:	1 user (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?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.023
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:

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 Arvid Requate

2013-07-09 15:54:38 CEST

It would be useful in some cases to be able to instruct the S4 Connector to skip synchronization of specific DNs, something like "global_ignore_dn". This would be useful e.g. to skip synchronization of gPLink attributes on containers like the LDAP-base or "OU=Domain Controllers" (see Bug 31600).

Comment 1 Stefan Gohmann

2017-06-16 20:40:04 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 2 Stefan Gohmann

2017-08-08 07:09:26 CEST

This issue has been filed against UCS 3.1.

UCS 3.1 is out of maintenance and many UCS components have vastly 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 this issue. In this case please provide detailed information on how this issue is affecting you.