Red Hat Bugzilla – Bug 781529
Managed Entry Plugin runs against managed entries upon any update without validating
Last modified: 2012-06-20 03:12:43 EDT
This bug is created as a clone of upstream ticket: https://fedorahosted.org/389/ticket/159 Managed Entries needs a method of validating that it is updating the managed entry due to some effected modification, rather than just 'any' modification to the parent object.
Steps to reproduce bug, and verify fix: [1] Create the template entry: dn: cn=UPG Template,dc=example,dc=com objectclass: mepTemplateEntry cn: UPG Template mepRDNAttr: cn mepStaticAttr: objectclass: posixGroup mepMappedAttr: cn: $uid mepMappedAttr: gidNumber: $gidNumber mepMappedAttr: description: User private group for $uid [3] Create the group: cn=groups,dc=example,dc=com [3] Set up mep config dn: cn=UPG Definition,cn=Managed Entries,cn=plugins,cn=config objectclass: extensibleObject cn: UPG Definition originScope: dc=example,dc=com originFilter: objectclass=posixAccount managedBase: cn=groups,dc=example,dc=com managedTemplate: cn=UPG Template,dc=example,dc=com [4] Create a user with objectclass=posixAccount (uid=original, dc=example,dc=com) [5] Check the modifytimestamp on the new entry (cn=original, cn=groups, dc=example,dc=com) [6] Modify the original entry(uid=original,dc=example,dc=com)- changing the "uidNumber" or any attribute that is not listed in the mep template(e.g. gidNumber or uid). [7] The modifytimestamp should not be updated, as the fix is to stop unnecessary changes to mep entries. Previously any update to the original entry would trigger an update on the managed entry. Mark
Bug is verified and the test cases are added to tet managed entry tet suit. All test cases are passing hence marking the bug as verified.
Since this bug is marked VERIFIED, I am clearing the needinfo flag
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: update an attribute in the origin entry that is not one of the Managed Entry attrbiutes Consequence: the managed entry is updated Fix: Don't update the managed entry unless the modifictation is on a manged entry attribute Result: The managed entry should be not updated if the mod on the origin is not a managed entry attribute
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. http://rhn.redhat.com/errata/RHSA-2012-0813.html