Netscape Certificate Management System 6.2, Administrator'S Manual

Page: 621 / 874

Setting Up Publishing
Chapter 15 Publishing 621
❍
If you are publishing everything to one location, create one publisher
specifying the location where you want to publish all files.
❍
If you are publishing to separate locations, create a publisher for each
location you will publish to specifying the location you will publish. You
can split these up by certificates and CRLs, or by even finer definitions.
You use Rules to determine which type to publish, and then tell the rule
which location to publish to by associating the Rule with the Publisher you
create in this step.
For complete details about setting up Publishers, see “Configuring Publishers
for Publishing to a File,” on page 623.
2.
For OCSP publishing, create a publisher for each location in the Online
Certificate Status Manager you will publish CRLs to.
❍
If you are publishing all CRLs to one location, create one publisher
specifying the location where you want to publish all CRLs.
❍
If you are publishing different types of CRLS to separate locations, create a
publisher for each location you will publish to specifying the location you
will publish. You use Rules to determine which type to publish, and then
tell the rule which location to publish to by associating the Rule with the
Publisher you create in this step.
For complete details about setting up Publishers, see “Configuring Publishers
for Publishing to OCSP,” on page 625.
3.
For LDAP publishing, you need a Publisher for each type of object you will be
publishing: CA certificate, cross-pair certificate, CRL, and user certificates. In
the case of LDAP publishing, the Publisher simply declares which attribute in
which to store the object. The attributes that are setup by default are the X500
standard attributes for storing each object type. You can change the attribute
you want to store the object by changing the attribute in this publisher.
Generally, you will not need to do anything to the Publishers for LDAP
publishing. For more information, see “Configuring Publishers for LDAP
Publishing,” on page 628.