| commit | 4a9cb8e4c6637d9b7cbc4282ac1e994f3725505d | [log] [tgz] |
|---|---|---|
| author | Patrick Williams <patrick@stwcx.xyz> | Mon Oct 04 12:08:55 2021 -0500 |
| committer | Patrick Williams <patrick@stwcx.xyz> | Mon Oct 04 12:32:47 2021 -0500 |
| tree | 461d53336b39f391b618b7bc507dc54acc5c4fb5 | |
| parent | ca1281170219b3027fd4f75a9c4e94a52fb16312 [diff] |
configure: simpify dbus policy install dir
Using the package config to find where dbus-1 installs its config files
is needless indirection and adds a hard build-time dependency on the
dbus-1 package, which isn't necessary. The `dbus-daemon` manpage
suggests that package-level configuration should be placed in
`/usr/share` and not `/etc`, so use `${datadir}` to place the config
files in that location.
Signed-off-by: Patrick Williams <patrick@stwcx.xyz>
Change-Id: I02f34bc05dda2cbeb6d7a3205b6fd9cb46bb9a67
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.
To build this package, do the following steps:
1. ./bootstrap.sh
2. ./configure ${CONFIGURE_FLAGS}
3. make
To clean the repository run `./bootstrap.sh clean`.
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.