| commit | cd30c496c8e4c9aec66e65ba16430dd2e0f86395 | [log] [tgz] |
|---|---|---|
| author | Marri Devender Rao <devenrao@in.ibm.com> | Wed Jun 12 01:40:17 2019 -0500 |
| committer | Marri Devender Rao <devenrao@in.ibm.com> | Fri Jul 05 04:04:37 2019 -0500 |
| tree | 57e9eb8885b160737e106452e7eb72c15d557ee3 | |
| parent | ffad1ef1c244b4a85da7c79dd550cfbb3d1ebeb8 [diff] |
Append private key from the system to CA signed certificate A CSR request is intiated which creates a private key file and CSR file in the system. CSR file is passed onto the CA to sign the certificate. If the CA signed certificate file does not have private key use the private key generated as part of the CSR request from the system. After sucessfull validation append the private key with the CA signed file and store in the system. Tested: 1) Verifid when uploading a certificate file without private key system is using the private key file from the system. Change-Id: I9a5313af64f87fdb1d9189558c95ab75ce317a73 Signed-off-by: Marri Devender Rao <devenrao@in.ibm.com>
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`.