
Chapter 14. Publishing
306
When a certificate is revoked, the server uses the publishing rules to locate and delete the
corresponding certificate from the LDAP directory or from the filesystem.
When a certificate expires, the server can remove that certificate from the configured directory. The
server does not do this automatically; the server must be configured to run the appropriate job. For
details, see
Chapter 18, Automated Jobs
.
14.2. Setting up Publishing
The general process to configure publishing is as follows:
1. For file publishing, create a publisher for each location to publish files.
There can be a single publisher or multiple publishers, depending on how many locations will be
used. The locations can be split by certificates and CRLs or finer definitions, such as certificate
type. Rules determine which type to publish and to what location by being associated with the
publisher.
For details about setting up publishers, see
Section 14.3.1, “Configuring Publishers for Publishing
to a File”
.
2. For OCSP publishing, create a publisher for each Online Certificate Status Manager to which
CRLs will be published.
There can be a single publisher or multiple publishers, depending on how many locations will be
used. Rules determine which type to publish and to what location by being associated with the
publisher.
For details about setting up publishers, see
Section 14.3.2, “Configuring Publishers for Publishing
to OCSP”
.
3. For LDAP publishing, there are three steps:
a. Configure the Directory Server to which certificates will be published. Refer to
Section 14.9,
“Configuring the Directory for LDAP Publishing”
.
b. Configure a publisher for each type of object published: CA certificates, cross-pair certificates,
CRLs, and user certificates. The publisher declares in which attribute to store the object.
The attributes set by default are the X.500 standard attributes for storing each object type.
This attribute can be changed in the publisher, but, generally, LDAP publishers do not need
changed. For more information, see
Section 14.3.3, “Configuring Publishers for LDAP
Publishing”
.
c. Set up mappers to enable an entry's DN to be derived from the certificate's subject name.
This generally does not need set for CA certificates, CRLs, and user certificates. There can
be more than one mapper set for a type of certificate. This can be useful, for example, to
publish certificates for two sets of users from different divisions of a company who are located
in different parts of the directory tree. A mapper is created for each of the groups to specify a
different branch of the tree.
For details about setting up mappers, see
Section 14.4.1, “Configuring Mappers”
.
4. Set rules to determine what certificates are published to the locations. Rules work independently,
not in tandem. A certificate or CRL that is being published is matched against every rule. Any
Содержание CERTIFICATE SYSTEM 7.2 - MIGRATION GUIDE
Страница 36: ...Chapter 1 Overview 16 Figure 1 4 Certificate System Architecture ...
Страница 144: ...124 ...
Страница 160: ...140 ...
Страница 208: ...188 ...
Страница 210: ...190 ...
Страница 256: ...236 ...
Страница 282: ...Chapter 12 Certificate Profiles 262 Parameter IssuerName_n IssuerType_n ...
Страница 285: ...Freshest CRL Extension Default 265 Parameter PointName_n PointIssuerName_n ...
Страница 335: ...Configuring Mappers 315 Figure 14 9 Selecting a New Mapper Type 6 Edit the mapper instance and click OK ...
Страница 362: ...342 ...
Страница 376: ...356 ...
Страница 436: ...416 ...
Страница 490: ...470 ...
Страница 504: ...484 ...