commit | d8b3790751d3f614ed5789cc429803de1f018f22 | [log] [tgz] |
---|---|---|
author | Nan Zhou <nanzhoumails@gmail.com> | Thu May 26 22:26:13 2022 +0000 |
committer | Nan Zhou <nanzhoumails@gmail.com> | Tue May 31 19:27:05 2022 +0000 |
tree | 188fb7eb9f915bb314b61305f8101a1090f954a9 | |
parent | 6aef160fc13e47343e96f9969166c3980e75f3b6 [diff] |
systemd: use qualified path Inspired by https://gerrit.openbmc.org/c/openbmc/phosphor-certificate-manager/+/54051 Tested: on real hardware, these binaries are in /usr/bin Signed-off-by: Nan Zhou <nanzhou@google.com> Change-Id: I7892cc0d416ca66bcda9ea6d58485dd66fb806a9
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.service
Purpose: Client certificate validation
./phosphor-certificate-manager --type=authority --endpoint=ldap \ --path=/etc/ssl/certs/authority --unit=bmcweb.service
Purpose: LDAP client certificate validation
./phosphor-certificate-manager --type=client --endpoint=ldap \ --path=/etc/nslcd/certs/cert.pem
phosphor-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.service
D-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.