Chapter 8. Publishing Certificates and CRLs
204
When publishing is enabled, every time a certificate or a CRL is issued, updated, or revoked, the
publishing system is invoked. The certificate or CRL is evaluated by the rules to see if it matches the
type and predicate set in the rule. The type specifies if the object is a CRL, CA certificate, or any other
certificate. The predicate sets more criteria for the type of object being evaluated. For example, it can
specify user certificates, or it can specify West Coast user certificates. To use predicates, a value
needs to be entered in the predicate field of the publishing rule, and a corresponding value (although
formatted somewhat differently) needs to be contained in the certificate or certificate request to match.
The value in the certificate or certificate request may be derived from information in the certificate,
such as the type of certificate, or may be derived from a hidden value that is placed in the request
form. If no predicate is set, all certificates of that type are considered to match. For example, all CRLs
match the rule if
CRL
is set as the type.
Every rule that is matched publishes the certificate or CRL according to the method and location
specified in that rule. A given certificate or CRL can match no rules, one rule, more than one rule, or all
rules. The publishing system attempts to match every certificate and CRL issued against all rules.
When a rule is matched, the certificate or CRL is published according to the method and location
specified in the publisher associated with that rule. For example, if a rule matches all certificates
issued to users, and the rule has a publisher that publishes to a file in the location
/etc/CS/
certificates
, the certificate is published as a file to that location. If another rule matches all
certificates issued to users, and the rule has a publisher that publishes to the LDAP attribute
userCertificate;binary
attribute, the certificate is published to the directory specified when
LDAP publishing was enabled in this attribute in the user's entry.
For rules that specify to publish to a file, a new file is created when either a certificate or a CRL is
issued in the stipulated directory.
For rules that specify to publish to an LDAP directory, the certificate or CRL is published to the entry
specified in the directory, in the attribute specified. The CA overwrites the values for any published
certificate or CRL attribute with any subsequent certificate or CRL. Simply put, any existing certificate
or CRL that is already published is replaced by the next certificate or CRL.
For rules that specify to publish to an Online Certificate Status Manager, a CRL is published to this
manager. Certificates are not published to an Online Certificate Status Manager.
For LDAP publishing, the location of the user's entry needs to be determined. Mappers are used to
determine the entry to which to publish. The mappers can contain an exact DN for the entry, some
variable that associates information that can be gotten from the certificate to create the DN, or enough
information to search the directory for a unique attribute or set of attributes in the entry to ascertain the
correct DN for the entry.
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 11, Setting Automated Jobs
.
Setting up publishing involves configuring publishers, mappers, and rules.
8.1.1. Publishers
Publishers
specify the location to which certificates and CRLs are published. When publishing to a
file, publishers specify the filesystem publishing directory. When publishing to an LDAP directory,
Содержание CERTIFICATE SYSTEM 8.0 - ADMINISTRATION
Страница 1: ...Red Hat Certificate System 8 0 Admin Guide Publication date July 22 2009 updated on March 25 2010 ...
Страница 42: ...20 ...
Страница 43: ...Part I Setting up Certificate Services ...
Страница 44: ......
Страница 190: ...168 ...
Страница 208: ...186 ...
Страница 223: ...Part II Additional Configuration to Manage CA Services ...
Страница 224: ......
Страница 256: ...234 ...
Страница 270: ...248 ...
Страница 280: ...258 ...
Страница 292: ...270 ...
Страница 293: ...Part III Managing the Subsystem Instances ...
Страница 294: ......
Страница 363: ...Managing RA Users 341 5 The user details page shows the person s UID full name email address and user SSL certificate ...
Страница 408: ...386 ...
Страница 438: ...416 ...
Страница 439: ...Part IV References ...
Страница 440: ......
Страница 503: ...Netscape Defined Certificate Extensions Reference 481 OID 2 16 840 1 113730 13 ...
Страница 504: ...482 ...
Страница 556: ...534 ...
Страница 564: ...542 ...