On 29 Jan 2021, at 19:54, Marco Favero <m.faverof(a)gmail.com>
> Since you are already using python, you could more easily just use lib389 directly
> than subprocess to dsconf btw:
> from lib389 import DirSrv
> import logging
I leave just a note on this...
Really at the moment I prefer trust on dsconf. I see that the lib389 documentation is
still work in progress.
Or it's not clear for me where to find the full documentation. For instance, here
it's not clear how to configure all uniqueness plugin parameters.
A more complete documentation seems the following:
I think simon has the most up to date documentation. Remember, dsconf itself relies on
lib389 so it can be trusted.
but for example it still lacks on some configurations about AttributeUniquenessPlugin,
such as "--subtree-entries-oc" which dsconf manages fine.
Another way to proceed is to manage all attributes and dn directly with LDAP modify
operations, but this would bypass lib389...
That's also a good approach, since cn=config is not subject to large amounts of
Thank you again for all the hints
389-users mailing list -- 389-users(a)lists.fedoraproject.org
To unsubscribe send an email to 389-users-leave(a)lists.fedoraproject.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
Senior Software Engineer, 389 Directory Server
SUSE Labs, Australia