| commit | 9fe64af47f6100266b4a0e234ff98d6e258bb150 | [log] [tgz] |
|---|---|---|
| author | Ravi Teja <raviteja28031990@gmail.com> | Mon Oct 12 10:54:56 2020 -0500 |
| committer | Ravi Teja <raviteja28031990@gmail.com> | Wed Oct 14 05:17:29 2020 +0000 |
| tree | 646ad2d0407fafbb5c139588fd75b44f65710aa9 | |
| parent | ea7c3f0c982f8ee50beaf282a4f4b0a32a90aed9 [diff] |
Fix build failure with feature flag "--enable-ca-cert-extension" There is an issue populating Makefile under bmc-vmi-ca directory. Unit test results: [==========] Running 4 tests from 1 test suite. [----------] Global test environment set-up. [----------] 4 tests from TestCACertMgr [ RUN ] TestCACertMgr.testObjectCreation [ OK ] TestCACertMgr.testObjectCreation (1 ms) [ RUN ] TestCACertMgr.testInvalidArgument [ OK ] TestCACertMgr.testInvalidArgument (1 ms) [ RUN ] TestCACertMgr.DeleteAllCSRObjects [ OK ] TestCACertMgr.DeleteAllCSRObjects (1 ms) [ RUN ] TestCACertMgr.DeleteObjectEntry [ OK ] TestCACertMgr.DeleteObjectEntry (0 ms) [----------] 4 tests from TestCACertMgr (3 ms total) [----------] Global test environment tear-down [==========] 4 tests from 1 test suite ran. (3 ms total) [ PASSED ] 4 tests. PASS ca_certs_manager_test (exit status: 0) Signed-off-by: Ravi Teja <raviteja28031990@gmail.com> Change-Id: I1d808439646bc91c137040b00299aaa0fd4e2a73
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.