Wednesday, April 5, 2023

[389-users] Re: ACME certificate and NSS databases

The "dsconf some-instance-name security" and dsctl commands can be used to manipulated the certs and keys used by the LDAP service:
9.3.3. Importing a Private Key and Server Certificate
9.3.4. Installing a Server Certificate
9.3. Managing the NSS Database Used by Directory Server
Plus run the system's "trust anchor" command so a PKI chain of trust is known by the local system.

Or, if the LDAP service is stopped, a new PEM cert can replace the existing SSL server cert in the NSS db using a certutil -A command, or a PKCS #12 file can be exported or imported into the NSS db ( pk12util -h )

For ACME, as a reference from the PKI server side of things, there is an example of an ACME responder from the upstream PKI project dogtag ( used for the Red Hat Certificate System / general purpose PKI solution ), and the suggested ACME clients are certbot and openshit-acme, in case it may provide with some ideas:
But of course any ACME compliant client should work just fine, it would be interesting to know more if anybody is using ACME for the LDAP SSL server certs, and what kind of validity dates are used.

Marc S.

On Wed, Apr 5, 2023 at 9:20 AM John Thurston <> wrote:

We currently use publicly-signed, and manually renewed, certificates on our internal directory servers. On other internal and external systems, we use public and private certificates handled by ACME-compliant agents.

I took a quick look, and was reminded that 389-Directory keeps its certs in an NSS database. Before I go hack together my own wrapper on certutil, I thought I'd ask:

Does anyone have a working ACME/Let's Encrypt agent they want to share?

--   --  Do things because you should, not just because you can.     John Thurston    907-465-8591  Department of Administration  State of Alaska
389-users mailing list --
To unsubscribe send an email to
Fedora Code of Conduct:
List Guidelines:
List Archives:
Do not reply to spam, report it:

No comments:

Post a Comment