Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1044171 - [RFE] Allow referential integrity suffixes to be configurable
[RFE] Allow referential integrity suffixes to be configurable
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base (Show other bugs)
7.0
Unspecified Unspecified
high Severity unspecified
: rc
: ---
Assigned To: Rich Megginson
Viktor Ashirov
: FutureFeature
Depends On: 1044173
Blocks: 1082754 1109759 1115294 1249775
  Show dependency treegraph
 
Reported: 2013-12-17 16:40 EST by Nathan Kinder
Modified: 2015-08-03 15:06 EDT (History)
5 users (show)

See Also:
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 04:32:14 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2015:0416 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 09:26:33 EST

  None (edit)
Description Nathan Kinder 2013-12-17 16:40:00 EST
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 08:02:39 EST
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 10:22:14 EST
Since bz 1044173 is verified, marking this one VERIFIED as well.
Comment 6 errata-xmlrpc 2015-03-05 04:32:14 EST
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

Note You need to log in before you can comment on or make changes to this bug.