diff options
| author | Nathan Kinder <nkinder@redhat.com> | 2010-10-01 14:11:20 -0700 |
|---|---|---|
| committer | Rich Megginson <rmeggins@redhat.com> | 2010-10-18 11:00:50 -0600 |
| commit | 5af5b5de59522a14c52b0273e6cef0b49e0758cb (patch) | |
| tree | 539d02514aa82398bf231647a8bb42d9f087763f | |
| parent | 9a95211bfc3e45fa72e3229f3c64e59fa42eced2 (diff) | |
| download | ds-5af5b5de59522a14c52b0273e6cef0b49e0758cb.tar.gz ds-5af5b5de59522a14c52b0273e6cef0b49e0758cb.tar.xz ds-5af5b5de59522a14c52b0273e6cef0b49e0758cb.zip | |
Bug 522055 - Scope check for managed attribute fails
When using the linked attribute plug-in, an entry that is renamed
that is outside of the scope of the plug-in will cause the forward
links in other entries to be updated if they contain a managed
attribute type.
We need to check if the new DN of the renamed entry is within the
scope of the configured linked attributes before updating forward
links.
(cherry picked from commit a82f61269d69882d19b15def70de68906ed5740e)
Branch: 389-ds-base-1.2.6
| -rw-r--r-- | ldap/servers/plugins/linkedattrs/linked_attrs.c | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/ldap/servers/plugins/linkedattrs/linked_attrs.c b/ldap/servers/plugins/linkedattrs/linked_attrs.c index 822f6c0e..5ac731c9 100644 --- a/ldap/servers/plugins/linkedattrs/linked_attrs.c +++ b/ldap/servers/plugins/linkedattrs/linked_attrs.c @@ -1928,7 +1928,8 @@ linked_attrs_modrdn_post_op(Slapi_PBlock *pb) linked_attrs_find_config_reverse(slapi_value_get_string(val), type, &config); - if (config) { + /* If the new DN is within scope, we should fixup the forward links. */ + if (config && slapi_dn_issuffix(new_dn, (config->scope))) { Slapi_ValueSet *vals = slapi_valueset_new(); slapi_valueset_add_value(vals, val); |