Testing Publishing To Files - Netscape MANAGEMENT SYSTEM 6.2 - ADMINISTRATOR Administrator's Manual

Testing Publishing to Files

To verify that the Certificate Manager is publishing certificates and CRLs correctly
to files, follow these steps:
Go to the end-entity interface and request a certificate.
1.
Go to the agent services interface and approve the request if you have an
2.
agent-approved enrollment configuration. If you set up automatic enrollment,
you can skip this step.
Download the certificate into your browser.
3.
Check whether the server generated the DER-encoded file containing the
4.
certificate.
To check whether the server published the certificate as a binary blob to the
specified directory, go to the directory you specified for the server to publish
certificates. You should see a file with name similar to
cert-<serial_number>.der
number of the certificate contained in the file.
Convert the DER-encoded certificate to its base 64-encoded format using the
5.
Binary to ASCII tool (see Chapter 8, "Binary to ASCII Tool" of CMS
Command-Line Tools Guide).
To convert the DER-encoded certificate to its base 64-encoded form:
a.
b.
c.
Open a command window.
Go to this directory:
<server_root>/bin/cert/tools
At the prompt, enter this:
substituting
<input_file>
encoded certificate and
the base-64 encoded certificate.
For example, if the file is in
want the base-64 encoded certificate to be in
C:\certificates\cert-1234.txt
BtoA C:\certificates\cert-1234.der
C:\certificates\cert-1234.txt
, where
<serial_number>
BtoA <input_file> <output_file>
with the path to the file that contains the DER
with the path to the file to write
<output_file>
C:\certificates\cert-1234.der
, the command would look like this:
Testing Publishing to Files
specifies the serial
and you
Chapter 15 Publishing 653