On Tue, Dec 16, 2025 at 3:02 PM Mark Reynolds <[email protected]> wrote: > Two things to try: > > [1] Change the filter to (remove the colon): > "(memberof=cn=large_group,ou=groups,dc=org,dc=com)"
removing the colon from the filer makes no difference. > > [2] Run the memberof fixup task: > > # dsconf slapd-YOUR_INSTANCE_NAME plugins memberof fixup "dc=org,dc=com" > > # dsconf slapd-YOUR_INSTANCE_NAME plugins memberof fixup-status --dn <DN > returned from the "fixup task"> --watch Thank you for this bit of information. After running these commands I found this event in the errors log: [16/Dec/2025:15:11:16.921403283 -0800] - INFO - memberof-plugin - memberof_fixup_task_thread - Memberof task starts (filter: "(|(objectclass=inetuser)(objectclass=inetadmin)(objectclass=nsmemberof))") ... Am I correct in interpreting this entry, in that the memberof fixup will only operate on object's which have the objectclass of either inetuser, inetadmin or nsmeberof ? I suppose I should have mentioned that I am running a custom schema that mimics what you'd expect to find in MS Active Directory where user objects have the following classes defined: objectClass: top objectClass: person objectClass: organizationalPerson objectClass: user My goal with this schema is to provide read only 389ds instances of what is found in my company's AD domain, by mirroring the attributes one would expect in AD, such as samaccountname, in 389ds. Assuming I am correct in this assumption, and that memberof fixup requires one of the above objectclasses found in that task filter, I can easily add that class to these user objects if necessary. Or perhaps there is a way to add one of my already defined objectclasses to the fixup process? Thank you, Bob -- _______________________________________________ 389-users mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected] Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
