From 621d9e5c413e561293d7484b93882d985b3fe15f Mon Sep 17 00:00:00 2001 From: Endi Sukma Dewata Date: Sat, 24 Mar 2012 02:27:47 -0500 Subject: Removed unnecessary pki folder. Previously the source code was located inside a pki folder. This folder was created during svn migration and is no longer needed. This folder has now been removed and the contents have been moved up one level. Ticket #131 --- .../admin/console/config/restorekeycertpanel.vm | 54 ++++++++++++++++++++++ 1 file changed, 54 insertions(+) create mode 100644 dogtag/common-ui/shared/admin/console/config/restorekeycertpanel.vm (limited to 'dogtag/common-ui/shared/admin/console/config/restorekeycertpanel.vm') diff --git a/dogtag/common-ui/shared/admin/console/config/restorekeycertpanel.vm b/dogtag/common-ui/shared/admin/console/config/restorekeycertpanel.vm new file mode 100644 index 000000000..8ef78bf36 --- /dev/null +++ b/dogtag/common-ui/shared/admin/console/config/restorekeycertpanel.vm @@ -0,0 +1,54 @@ + + + +

Import 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) need to be imported. For a software token, all of these keys and certificates are stored in a single file in the PKCS #12 format which is protected by the password provided during the creation of this file. To import this PKCS #12 file, first copy the PKCS #12 file to the alias directory for the cloned subsystem. Then enter an appropriate filename and password in the form specified below. +

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

+For keys and certificates stored in an external software token, please refer to the Dogtag documentation for instructions. +

+By default, if the path is left blank, no PKCS #12 file will be imported. +
+#if ($errorString != "") + $errorString +#end + + + + + + + + + + + +
PKCS #12 filename:
PKCS #12 Password:
+
-- cgit