commit | 7047be6784455faa71f16ebbc66a74040634e350 | [log] [tgz] |
---|---|---|
author | Nan Zhou <nanzhoumails@gmail.com> | Thu Mar 10 12:34:06 2022 -0800 |
committer | Nan Zhou <nanzhoumails@gmail.com> | Tue Mar 29 18:30:49 2022 +0000 |
tree | 6920e93cdc13f7afb6c6fd31ee34d02b299b83bd | |
parent | 447d55d6870f12d75801c3fb2c3a127b61e169d0 [diff] |
argument parser: use CLI11 and add unit tests CLI11 is one of the most commonly use argument parser in OpenBMC. It can save ~150 lines of codes in this project. We are hitting argument related bugs that not covered in unit tests. This test adds a test for argument parsing. Tested: QEMU IPMI/Redfish worked. Signed-off-by: Nan Zhou <nanzhoumails@gmail.com> Change-Id: Ib409c7e6a82ad31049f2da3e32727ebdf185f0fc
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.