This bug is created as a clone of upstream ticket:
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:
 Create the template entry:
dn: cn=UPG Template,dc=example,dc=com
cn: UPG Template
mepStaticAttr: objectclass: posixGroup
mepMappedAttr: cn: $uid
mepMappedAttr: gidNumber: $gidNumber
mepMappedAttr: description: User private group for $uid
 Create the group:
 Set up mep config
dn: cn=UPG Definition,cn=Managed Entries,cn=plugins,cn=config
cn: UPG Definition
managedTemplate: cn=UPG Template,dc=example,dc=com
 Create a user with objectclass=posixAccount (uid=original, dc=example,dc=com)
 Check the modifytimestamp on the new entry (cn=original, cn=groups, dc=example,dc=com)
 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).
 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.
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.
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.