Ssl Server Key Pair And Certificate - Netscape MANAGEMENT SYSTEM 6.0 Installation And Setup Manual

Hide thumbs Also See for NETSCAPE MANAGEMENT SYSTEM 6.0:
Table of Contents

Advertisement

<token_name>
and the certificate. If you used the internal/software token, use
Key Storage Token
For example, your edited entries might look like this:
ca.crl_signing.cacertnickname=crlSigningCert cert-demoCA
ca.crl_signing.defaultSigningAlgorithm=MD5withRSA
ca.crl_signing.tokenname=Internal Key Storage Token
Save your changes and close the file.
e.
Restart the Certificate Manager. Now the Certificate Manager is ready to use
4.
the CRL signing certificate to sign the CRLs it generates.

SSL Server Key Pair and Certificate

Every Certificate Manager you have installed has at least one SSL server certificate.
The first time you generated this certificate is when you installed the Certificate
Manager. The default nickname for the certificate is
Server-Cert cert-<instance_id>
instance in which the Certificate Manager is installed.
The Certificate Manager's SSL server certificate was issued by the CA to which you
submitted the certificate signing request. You might have submitted the request to
the Certificate Manager itself, another internally deployed CA, or a public CA. To
find out the issuer name, follow the instructions in "Viewing the Certificate
Database Content" on page 482.
The Certificate Manager uses its SSL server certificate to do SSL server-side
authentication to the following:
The End-Entity Services interface (the HTTPS port)
The Certificate Manager Agent Services interface
Clone Certificate Managers, when used as a master Certificate Manager in a
cloned CA setup (see "Cloning a Certificate Manager" on page 282)
By default, the Certificate Manager uses a single SSL server certificate for
authentication purposes. However, you can request and install additional SSL
server certificates for the Certificate Manager. For example, you can configure the
Certificate Manager to use separate server certificates for authenticating to the
End-Entity Services interface and Agent Services interface. For instructions, see
"Configuring the Server to Use Separate SSL Server Certificates" on page 459.
with the name of the token used for generating the key pair
as the value.
, where
Chapter 14
Keys and Certificates for the Main Subsystems
identifies the CMS
<instance_id>
Managing CMS Keys and Certificates
Internal
425

Advertisement

Table of Contents
loading

This manual is also suitable for:

Certificate management system 6.0

Table of Contents