RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1044171 - [RFE] Allow referential integrity suffixes to be configurable
Summary: [RFE] Allow referential integrity suffixes to be configurable
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: 389-ds-base
Version: 7.0
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Rich Megginson
QA Contact: Viktor Ashirov
URL:
Whiteboard:
Depends On: 1044173
Blocks: 1082754 1109759 1115294 1249775 2084180
TreeView+ depends on / blocked
 
Reported: 2013-12-17 21:40 UTC by Nathan Kinder
Modified: 2022-05-11 15:23 UTC (History)
5 users (show)

Fixed In Version: 389-ds-base-1.3.3.1-1.el7
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-05 09:32:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 389ds 389-ds-base issues 864 0 None None None 2020-09-13 20:46:44 UTC
Red Hat Product Errata RHSA-2015:0416 0 normal SHIPPED_LIVE Important: 389-ds-base security, bug fix, and enhancement update 2015-03-05 14:26:33 UTC

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
Note You need to log in before you can comment on or make changes to this bug.