From edf9c2273c00b52b0c240bc0c75dc1ba7bdc396e Mon Sep 17 00:00:00 2001 From: Endi Sukma Dewata Date: Fri, 9 Nov 2012 01:51:54 -0500 Subject: Reorganized common templates. The common templates have moved from common-ui into base/common. The deployment tools have been updated to use the new location. Ticket #407 --- .../pki/admin/console/config/backupkeycertpanel.vm | 57 ++++++++++++++++++++++ 1 file changed, 57 insertions(+) create mode 100644 base/common/shared/webapps/pki/admin/console/config/backupkeycertpanel.vm (limited to 'base/common/shared/webapps/pki/admin/console/config/backupkeycertpanel.vm') diff --git a/base/common/shared/webapps/pki/admin/console/config/backupkeycertpanel.vm b/base/common/shared/webapps/pki/admin/console/config/backupkeycertpanel.vm new file mode 100644 index 000000000..3ec3526d1 --- /dev/null +++ b/base/common/shared/webapps/pki/admin/console/config/backupkeycertpanel.vm @@ -0,0 +1,57 @@ + + + +

Export Keys and Certificates

+

+To setup a cloned subsystem, the master subsystem's keys and certificates (with the exception of the SSL server key and certificate) as well as the CA certificate chains need to be exported, and later imported into the cloned subsystem. All of these keys and certificates are stored in a single file in the PKCS #12 format which is protected by the password specified below. This export operation is performed only when the master subsystem's keys and certificates are stored in the software token. +

+If these keys and certificates are stored in a hardware token, the hardware token vendor needs to be consulted for information on how to export them. +

+For cloning, if the keys and certificates are stored in a hardware token, clones should use the same hardware token as that of the Master. +

+#if ($errorString != "") + $errorString +#end +
+ Export subsystem keys and certificates +
+ + + + + + + + + + + +
Password to protect the PKCS #12 file:
Password again:
+
+ Don't export subsystem keys and certificates +
-- cgit