| commit | a3bb38fb26716fadbe65ac234776e5e86409a121 | [log] [tgz] |
|---|---|---|
| author | Zbigniew Kurzynski <zbigniew.kurzynski@intel.com> | Tue Sep 17 13:34:25 2019 +0200 |
| committer | Zbigniew Kurzynski <zbigniew.kurzynski@intel.com> | Wed Nov 06 07:11:52 2019 +0000 |
| tree | 17444e638582af1c38540667d54da2a98373a34b | |
| parent | 3b07b77a58820b27c32981e36b0ce500dffaa94c [diff] |
Certificate delete API – backend. Till now the Certificate Manager has one-to-one relation with a Certificate class. And the DELETE API provided by the Certificate Manager was enough to delete managed by it certificate. With introducing Mutual-TLS the relation is changing to one-to-many and current delete API is not sufficient. This commit adds DELETE interface to Certificate class, so each of them can be removed individually. This implementation was done on base of current user account management implementation. The Certificate class exposes the delete interface on DBus. When the API is called the Certificate instance calls proper operation on Certificate Manager which removes it from its internal collection. The rest of the removing certificate process, including service reset remains as it was. Tested with uploaded multiple TLS certificates. Each Certificate exposes Delete interface on dbus and user is able to delete each of them. The delete API on Certificate Manager object was replaced with DeleteAll interface and results in deleting all loaded certificates. Signed-off-by: Zbigniew Kurzynski <zbigniew.kurzynski@intel.com> Change-Id: I9dd6fa998e8bd8081fbd13549831bc94a4a7aa54
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`.