Netscape NETSCAPE MANAGEMENT SYSTEM 4.5, Installation And Setup Manual

Page: 302 / 866

Cloning a Certificate Manager
302 Netscape Certificate Management System Installation and Setup Guide • October 2001
❍
SHA-1 with DSA generates a 160-bit message digest. Before choosing
SHA-1 with DSA, make sure your applications support it. Communicator
4.0 (or later) and Netscape server products with a version number greater
than 4.0 support it.
Before selecting an algorithm, make sure that Certificate Manager has the
algorithm enabled.
4.
Click Display to examine the CRL (before updating it).
The CRL appears in the browser window. In the list, look for the certificate
revoked by the clone Certificate Manager. If you don’t see the certificate, check
logs to resolve the problem.
5.
If you want to update the CRL with the latest certificate revocation
information, use the browser’s Back button to return to the previous page and
click Update.
Step 10. Use Master CA’s Agent Certificate in
Clone CAs
This step is optional.
The procedure below explains how to use the master Certificate Manager’s agent
certificate for a clone Certificate Manager (instead of creating a new agent
certificates for clone CAs).
1.
Go to the configuration directory of a cloned CA:
<server_root>/cert-<instance_id>config
2.
Open the configuration file (
CMS.cfg
) in a text editor.
3.
Locate this line:
agentgateway.enableAdminEnroll=true
4.
Change the value to
false
:
agentgateway.enableAdminEnroll=false
This configures the cloned CA in to a mode where it expects a certificate (that
was already issued and chains properly) to be presented when you access its
agent interface.
5.
Restart the clone CA.
6.
Use Netscape Console and open the CMS window for the clone CA instance.