HTTPS on internal networks (was Industry standard)

Posted Jun 15, 2026 11:51 UTC (Mon) by anselm (subscriber, #2796)
In reply to: HTTPS on internal networks (was Industry standard) by pizza
Parent article: Larson: Are insecure code completions a vulnerability?

We have an internal OpenLDAP server on ldap.example.com (the actual domain name is obviously different) which uses LDAPS and/or STARTTLS. To maintain a certificate for that server we use Caddy to host a simple phonebook-type UI on https://ldap.example.com. Caddy gets a certificate for ldap.example.com from our internal ACME-based CA and keeps it up to date. There is a systemd path unit that watches the Caddy certificate directory for ldap.example.com, and if the certificate file changes, it (and its associated private key and intermediate certificate) are copied to the OpenLDAP server and the OpenLDAP server is restarted.

This approach would be reasonably easy to generalise and would also work with CertBot or similar tools instead of Caddy. (We have Caddy on the machine, anyway, because of other things, so having it do a little extra work is no problem.)

---