Bug 747403

Summary: Allow automember to work on entries that have already been added
Product: [Retired] 389 Reporter: Nathan Kinder <nkinder>
Component: Server - PluginsAssignee: Rich Megginson <rmeggins>
Status: CLOSED CURRENTRELEASE QA Contact: Chandrasekar Kannan <ckannan>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 1.2.9CC: benl
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: 389-ds-base-1.2.11.1-1.fc17 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 768084 (view as bug list) Environment:
Last Closed: 2013-03-04 23:36:25 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 495079, 690319, 768084    

Description Nathan Kinder 2011-10-19 17:46:26 UTC
The automember plug-in currently checks ADD operations to see if the entry matches one of the defined automember rules.  Existing entries are not checked when they are modified to avoid a performance impact to modify operations.  We should provide a way to have the automember plug-in check existing entries to see if any automember work needs to be done.  This is something that the FreeIPA project would like to see.

A good way of accomplishing this would be to add a task to the automember plug-in.  The creator of the task would provide a search filter and base.  All matching entries would be checked against the defined automember rules to see if they should be added to any groups.  This allows one to add the triggering attributes/values after the entry was initially added, and then trigger the task to perform automember updates.  The nice thing about this approach is that we don't cause any negative performance impact on normal modify operations.

Comment 3 Martin Kosek 2012-01-04 13:18:27 UTC
Upstream ticket:
https://fedorahosted.org/389/ticket/20

Comment 4 Nathan Kinder 2013-03-04 23:36:25 UTC
This was fixed in 389-ds-base-1.2.11.1-1.fc17.  Closing.