| commit | dc91fb61e5056d0ee508caf0356ff44e735f11e2 | [log] [tgz] |
|---|---|---|
| author | Jayanth Othayoth <ojayanth@in.ibm.com> | Tue May 04 23:17:47 2021 -0500 |
| committer | Jayanth Othayoth <ojayanth@in.ibm.com> | Tue May 04 23:17:47 2021 -0500 |
| tree | 5ba35acee8870d54788bc7894c1815db62198ec0 | |
| parent | 641a559eea55832c1e8adc807d2d693c1a40f0c6 [diff] |
Add fix for Missing "OU" OrganizationalUnit CSR generateCSR function missed to include the "OU" field information during CSR generation. Fix is to add this missing field in the CSR. Details available in issue #phosphor-certificate-manager/18 Tested: Created CSR string and verified "OU" field is present. Signed-off-by: Jayanth Othayoth <ojayanth@in.ibm.com> Change-Id: I70a7d53f85b01241b91e40e666539c194e217973
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.