Certificate management allows to replace the existing certificate and private key file with another (possibly CA signed) Certificate key file. Certificate management allows the user to install both the server and client certificates.
This project can be built with meson. The typical meson workflow is:
meson builddir && ninja -C builddir.
Multiple instances of phosphor-certificate-manager are usually run on the bmc
to support management of different types of certificates.
Usage: ./phosphor-certificate-manager [options]
Options:
--help Print this menu
--type certificate type
Valid types: client,server,authority
--endpoint d-bus endpoint
--path certificate file path
--unit=<name> Optional systemd unit need to reload
Purpose: Server https certificate
./phosphor-certificate-manager --type=server --endpoint=https \
--path=/etc/ssl/certs/https/server.pem --unit=bmcweb.servicePurpose: Client certificate validation
./phosphor-certificate-manager --type=authority --endpoint=truststore \
--path=/etc/ssl/certs/authority --unit=bmcweb.servicePurpose: LDAP client certificate validation
./phosphor-certificate-manager --type=client --endpoint=ldap \
--path=/etc/nslcd/certs/cert.pemphosphor-certificate-manager is an implementation of the D-Bus interface
defined in
this document.
D-Bus service name is constructed by "xyz.openbmc_project.Certs.Manager.{Type}.{Endpoint}" and D-Bus object path is constructed by "/xyz/openbmc_project/certs/{type}/{endpoint}".
Take https certificate management as an example.
./phosphor-certificate-manager --type=server --endpoint=https \
--path=/etc/ssl/certs/https/server.pem --unit=bmcweb.serviceD-Bus service name is "xyz.openbmc_project.Certs.Manager.Server.Https" and D-Bus object path is "/xyz/openbmc_project/certs/server/https".
OpenBMC bmcweb exposes various
REST APIs
for certificate management on the BMC, which leverages functionalities of
phosphor-certificate-manager via D-Bus.