#47529 Automember plug-in should treat MODRDN operations as ADD operations
Closed: Fixed None Opened 6 years ago by nkinder.

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.

Is there some reason post_e was changed to port_e?

Replying to [comment:6 rmeggins]:

Is there some reason post_e was changed to port_e?

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
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

Metadata Update from @mreynolds:
- Issue assigned to mreynolds
- Issue set to the milestone: 1.3.3 - 11/13 (November)

3 years ago

Login to comment on this ticket.