Digital Certificate Manager (DCM) allows you to define and manage Certificate Revocation List (CRL) location information for a specific Certificate Authority (CA) to use as part of the certificate validation process.
DCM, or an application that requires CRL processing, can use the CRL to determine that the CA that issued a specific certificate has not revoked the certificate. When you define a CRL location for a specific CA, applications that support the use of certificates for client authentication can access the CRL.
Applications that support the use of certificates for client authentication can perform CRL processing to ensure more stringent authentication for certificates that they accept as valid proof of identity. Before an application can use a defined CRL as part of the certificate validation process, the DCM application definition must require that the application perform CRL processing.
How CRL processing works
When you use DCM to validate a certificate or application, DCM performs CRL processing by default as part of the validation process. If there is no CRL location defined for the CA that issued the certificate that you are validating, DCM cannot perform CRL checking. However, DCM can attempt to validate other important information about the certificate, such as that the CA signature on the specific certificate is valid and that the CA that issued it is trusted.
Define a CRL location
To define a CRL location for a specific CA, follow these steps:
Having defined a location for a CRL for a specific CA, DCM or other applications can use it when performing CRL processing. However, before CRL processing can work, the Directory Services server must contain the appropriate CRL. Also, you must configure both the Directory Server (LDAP) and client applications to use SSL, and assign a certificate to the applications in DCM.