Bug 1044171

Summary:	[RFE] Allow referential integrity suffixes to be configurable
Product:	Red Hat Enterprise Linux 7	Reporter:	Nathan Kinder <nkinder>
Component:	389-ds-base	Assignee:	Rich Megginson <rmeggins>
Status:	CLOSED ERRATA	QA Contact:	Viktor Ashirov <vashirov>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	7.0	CC:	lkrispen, nhosoi, nkinder, pspacek, vashirov
Target Milestone:	rc	Keywords:	FutureFeature
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	389-ds-base-1.3.3.1-1.el7	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-03-05 09:32:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1044173
Bug Blocks:	1082754, 1109759, 1115294, 1249775, 2084180

Description Nathan Kinder 2013-12-17 21:40:00 UTC

This bug is created as a clone of upstream ticket:
https://fedorahosted.org/389/ticket/47527

 The referential integrity plug-in currently doesn't allow you to restrict the suffixes it applies to. It would be nice to be able to list the suffixes to include or exclude for referential integrity operations operations.

The specific scenario where this would be useful is when a MODRDN operation is performed to move an entry.  If an entry is moved outside of the scope of the referential integrity plug-in, any references to that entry should be removed.

When an entry outside of the scope of the referential integrity plug-in is deleted, we don't need to bother searching for references at all.

The difficulty with implementing this is that the current way we configure the referential integrity plug-in uses an argc/argv approach.  This doesn't lend itself well to remaining backwards compatible.  If we need to add new suffix scoping config attributes, they should be actual named configuration attributes so we can leave the existing configuration attributes as-is.  We could also add the ability to use an alternate config area and convert entirely to named config attributes if an alternate config area is being used, but retain the argc/argv approach if the configuration is in the main config entry.

This functionality is needed by FreeIPA for a user provisioning feature that is being designed.

Comment 3 Ludwig 2014-11-18 13:02:39 UTC

this bug can be considered as a subset of bz 1044173, which extended the flexibility and configuration options of the referential integrity plugin further.

I don't think this bz needs extra testing if 1044173 is verified

Comment 4 Viktor Ashirov 2014-11-25 15:22:14 UTC

Since bz 1044173 is verified, marking this one VERIFIED as well.

Comment 6 errata-xmlrpc 2015-03-05 09:32:14 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0416.html