Chapter 2. Installation and Configuration
54
Figure 2.17. Supplying the Key and Certificate Information
NOTE
When cloning a CA, the master and clone instances have the same CA signing key.
6. The subsystem information is automatically supplied from the master instance to the clone
instance once the keys are successfully restored. Complete the configuration process.
7. Restart the clone instance.
/etc/init.d/
instance-id
restart
For more information on using cloning as part of a deployment strategy, see
Chapter 19, Configuring
the Certificate System for High Availability
.
2.8. Silent Installation
The Certificate System includes a tool,
pkisilent
, which can completely create and configure an
instance. Normally, adding instances requires running the
pkicreate
utility to create the instance
and then accessing the subsystem HTML page to complete the configuration. The
pkisilent
utility creates and configures the instance in a single step. The
pkisilent
tool is downloaded
independently from the Certificate System packages. It is available through the
Red Hat Certificate
System 7.2
Red Hat Network channel.
NOTE
Run this tool on a system which already has a subsystem installed, since this tool
depends on having libraries, JRE, and core jar files already installed.
The silent installation tool has the following format:
perl pkisilent Configure
subsystem_type -options
Summary of Contents for CERTIFICATE SYSTEM 7.2 - MIGRATION GUIDE
Page 36: ...Chapter 1 Overview 16 Figure 1 4 Certificate System Architecture ...
Page 144: ...124 ...
Page 160: ...140 ...
Page 208: ...188 ...
Page 210: ...190 ...
Page 256: ...236 ...
Page 282: ...Chapter 12 Certificate Profiles 262 Parameter IssuerName_n IssuerType_n ...
Page 285: ...Freshest CRL Extension Default 265 Parameter PointName_n PointIssuerName_n ...
Page 362: ...342 ...
Page 376: ...356 ...
Page 436: ...416 ...
Page 490: ...470 ...
Page 504: ...484 ...