It works! I figured out why I wasn't getting logging in the first place and convinced myself the plugin was actually running. What I can't figure out is why it didn't seem to be working before, but now it does seem to be working. Very strange, but clearly operator error of some sort.
Can you tell me if the fixup process needs to be run manually on a regular basis or does the plugin "hook" changes once it is up and running? I may have been triggering the fixup process incorrectly if it must be run regularly. Thanks again for the help and sorry for any confusion. Craig On Tue, Sep 8, 2015 at 2:52 PM, Mark Reynolds <[email protected]> wrote: > > > On 09/08/2015 03:31 PM, Craig Setera wrote: > > I did restart the server. The following is an example of a user entry: > > dn: [email protected],ou=demo,ou=People,dc=demo,dc=com > objectClass: accountPolicy > objectClass: inetOrgPerson > objectClass: inetUser > objectClass: nuxeoUser > objectClass: organizationalPerson > objectClass: person > objectClass: pwmUser > objectClass: top > cn: Craig Setera > sn: Setera > givenName: Craig > mail: [email protected] > uid: [email protected] > > Here is an example of a group: > > dn: cn=administrators,ou=demo,ou=Groups,dc=demo,dc=com > objectClass: groupOfUniqueNames > objectClass: top > cn: administrators > uniqueMember: [email protected],ou=demo,ou=People,dc=demo,dc=com > > The problem that I'm seeing is that having looked at the plugin's source > code, I would have expected to at least see this message in the log even if > things were misconfigured: > > slapi_log_error( SLAPI_LOG_TRACE, MEMBEROF_PLUGIN_SUBSYSTEM, > "--> memberof_postop_init\n" ); > >
-- 389 users mailing list [email protected] https://admin.fedoraproject.org/mailman/listinfo/389-users
