What did you have in mind here? path to client certs in the .dsrc or similar? lib389 already supports cert auth so it should just need wiring in ...

What did you have in mind here? path to client certs in the .dsrc or similar? lib389 already supports cert auth so it should just need wiring in ...

Yeah, I think we should support both - .dsrc and direct CLI options for dsconf and dsidm.
Also, we can check other parts like plugins, replication monitor (still in development), etc. Just to be sure that everywhere where we can use the certificate-based authentication - it is covered.

dsrc and dsconf/dsidm already support the layering of options you desire. Look at src/lib389/lib389/cli_base/dsrc.py and how that inlines the options. When we take the clientcert option, we would have dsrc_to_ldap handle setting up the instance with the right auth.

For the replmonitor and cert auth, the best way would be to have repl monitor to use dsrc and the cli so that they could inherit the same code, and then it will just work :)

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

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.