
then Revoke Certificate.
Once a reason for revocation
is provided and the certificate
has been revoked, it is moved
from the Issued Certificates
queue to the Revoked
Certificates queue. The
properties of the revoked
certificate will provide new
details showing the certificate
has truly been revoked.
The act of revoking a
certificate itself doesn’t place
the certificate in the CRL until
the next publish of the CRL
occurs. Publishing of the CRL
can occur instantly via a manual “Publish” task.
Otherwise, an automatic publish of
the CRL will occur based on the CRL
publishing parameters. In this
example, the publishing interval is
set to occur every hour.
CRL Distribution Point
(CDP)
Certificate validation is critical to a
correctly functioning public key
infrastructure (PKI). As a security
best practice, certificate validation
should fail if clients aren’t able to
locate and/or gain access to the
CRL to check certificate revocation
status. This is the exact behavior of
Security Manager that relies upon CRL access to
continually assess the CA signed certificate for validity.
In the last section, we’ve walked through the revocation
of an issued certificate and the publishing of the CRL to
reflect the revoked certificate. So, how does a client
receive CRL location information in order to continually
validate an installed certificate?
The answer: In the certificate. After a Certificate
Authority is installed, CRL Distribution Point (CDP)
extensions must be configured before the CA issues any
certificates. The CDP extension specifies where to find
up-to-date CRLs that are signed by the CA. These extensions apply to all certificates that are issued
by that CA. Configuring the CDP is made possible via the Extensions tab of the Certificate Authority
properties window.
Comentarios a estos manuales