When a MODRDN operation moves an entry into the configured scope of the automember plug-in, we should process the automember rules just as we do for an ADD operation. If the entry is already within the automember scope and is being moved elsewhere, the automember should just ignore it as it does today.
This functionality is needed by FreeIPA for a user provisioning feature that is being proposed.
attachment 0001-Ticket-47529-Automember-plug-in-should-treat-MODRDN-.patch
Is there some reason post_e was changed to port_e?
Replying to [comment:6 rmeggins]:
It should be post_e. I had changed it to something else, and then "tried" to restore it to the original value.
git merge ticket47529 Updating b1fad4e..87115fa Fast-forward ldap/servers/plugins/automember/automember.c | 54 ++++++++++++++++++++++--- 1 files changed, 47 insertions(+), 7 deletions(-)
git push origin master Counting objects: 13, done. Delta compression using up to 4 threads. Compressing objects: 100% (7/7), done. Writing objects: 100% (7/7), 1.05 KiB, done. Total 7 (delta 4), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/ds.git b1fad4e..87115fa master -> master
commit 87115fa Author: Mark Reynolds mreynolds@redhat.com Date: Tue Nov 19 20:51:08 2013 -0500
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1044196
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.3 - 11/13 (November)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/866
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.