Table of Contents
Advertisement
Password Storage
Each subsystem stores passwords for its internal database, and for the tokens
containing its keys and certificates. See "System Passwords," on page 252 for
information on how these passwords are stored.
Tokens
You choose either the
token) or an external token to store the signing certificate and key pair and the SSL
signing certificate and key pair.
If you are using an external token, you will need to install it before you run the
Installation Wizard. In the wizard, you can select from a list of already installed
and available tokens. For example,
Token" on page 316.
Internal Database
Each subsystem uses an internal database to store information (such as certificates
and certificate requests) used by the subsystem you will be installing in this CMS
instance. By default, a separate internal database is created for each subsystem you
configure. You can choose to use the same internal database for more than one
subsystem by specifying this when running the installation wizard to configure
that subsystem. You should carefully consider whether you want to store this
information in a separate internal database for each subsystem or use one internal
database for all subsystems installed on the host.
It's recommended that you do not use this Directory Server instance for any other
purposes; the directory schema will be configured for storing CMS data.
Signing Key Type and Length
If you wish, you can import the signing key and certificate used in a previous
version of CMS installation rather than generating a new signing key pair. For
information on how to do this, check the migration information in Step 6 of the
section "Upgrading" in Chapter 2 of the Command-Line Tools Guide.
Online Certificate Status Manager Deployment Considerations
token (if you plan to use the internal/software
internal
. For installation instructions, see "External
HSM
Chapter 5
OCSP Responder
175
Advertisement
Table of Contents
