fixup-memberof.pl help says, "-f filter: Filter for entries to fix up, If omitted, all entries under the specified base will have their memberOf attribute regenerated".
It seems the filter option uses 'objectClass=inetuser' by default (it renames only entries that matches the default filter) and if this condition is not met, it wont rename the entries.
Adding more clarification to the 'filter' option would really help when someone allows 'memberof' in some other objectClass and do not use inetUser objectClass at all.
Steps to Reproduce: 1. Use an objectClass that allows 'memberof' attribute (and no inetUser objectClass) in a user entry (eg: objectClass=ipaHost, this allows memberof) 2. Add the user to a group 3. Enable memberof plugin. 4. Run fixup-memberof.pl to add 'memberof' attribute.
Actual results: fixup-memberof.pl fixes ony user entries with inetUser objectClass.
Expected results: fixup-memberof.pl fixes all user entries that allows 'memberof' attribute. Currnetly this is possibly by mentioning a filter to override the default(-f option) however this is not documented in the help output or man page.
attachment 0001-Ticket-47315-filter-option-in-fixup-memberof-require.patch
git merge ticket47315 Updating db6bcd7..de61f34 Fast-forward ldap/admin/src/scripts/fixup-memberof.pl.in | 4 ++-- ldap/servers/plugins/memberof/memberof.c | 2 +- man/man8/fixup-memberof.pl.8 | 3 ++- 3 files changed, 5 insertions(+), 4 deletions(-)
git push origin master Counting objects: 27, done. Delta compression using up to 4 threads. Compressing objects: 100% (13/13), done. Writing objects: 100% (14/14), 1.55 KiB, done. Total 14 (delta 9), reused 0 (delta 0) To ssh://git.fedorahosted.org/git/389/ds.git db6bcd7..de61f34 master -> master
commit de61f34
Metadata Update from @mreynolds: - Issue assigned to mreynolds - Issue set to the milestone: 1.3.1
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/652
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.