Create certificate management page
Displays certificates and the ability to add up to one
of each type of certificate (as limited by the backend
implementation). HTTPS certificate and LDAP client cert
are implemented in this commit, with the ability to add
more types as needed by adding them to the constants.js
CERTIFICATE_TYPES array.
Also provides the ability to replace a certificate once
it is added.
Resolves openbmc/phosphor-webui#43
Tested: loaded onto a witherspoon and able to view and
replace both the HTTPS certificate and the
LDAP certificate. GUI only allows to upload an
LDAP certificate if one doesn't already exist.
The GUI limits the user to one file per type as
expected at this time and provides the
appropriate validation messages. Alert messages
appear above the table if the certificate is
expired or within 30 days of expiring.
Change-Id: I345267280ecd3cb257e9304886cde9ebb69b1240
Signed-off-by: beccabroek <beccabroek@gmail.com>
Signed-off-by: Yoshie Muranaka <yoshiemuranaka@gmail.com>
diff --git a/app/common/services/constants.js b/app/common/services/constants.js
index dd1012c..dabbc77 100644
--- a/app/common/services/constants.js
+++ b/app/common/services/constants.js
@@ -20,6 +20,17 @@
SUCCESS_STATUS: 'ok',
SUCCESS_MESSAGE: '200 OK'
},
+ CERTIFICATE_TYPES: [
+ {
+ 'Description': 'HTTPS Certificate',
+ 'location':
+ '/redfish/v1/Managers/bmc/NetworkProtocol/HTTPS/Certificates'
+ },
+ {
+ 'Description': 'LDAP Certificate',
+ 'location': '/redfish/v1/AccountService/LDAP/Certificates'
+ }
+ ],
CHASSIS_POWER_STATE: {
on: 'On',
on_code: 'xyz.openbmc_project.State.Chassis.PowerState.On',