Skip to main content
Skip table of contents

CC user interface in Certificate Manager

The Certificate Controller (CC) in Certificate Manager is used by officers to publish and manage publications, activate OCSP, revoke, and reinstate certificates either individually or in groups.

The CC user interface shows a number of certificates with various status as the result of a search.


Reason codes

Certificates can be published and revoked for various reasons. Each reason code has its own icon, which is used as a graphical indicator in the CC application window. All reason codes in the following table may not appear in your CC. Reason codes will only appear if the configuration has been set accordingly.

Public key certificate icons have a green border while attribute certificates have a blue border.

Reason code



Key compromise


Used in revoking an end-entity certificate. It indicates that it is known or suspected that the subject's private key, or other aspects of the subject validated in the certificate, have been compromised.

Affiliation changed


The subject's name or other information in the certificate has been modified. There is no cause to suspect that the private key has been compromised.



The certificate has been superseded. There is no cause to suspect that the private key has been compromised.

Cessation of operation


The certificate is no longer needed for the purpose for which it was issued. There is no cause to suspect that the private key has been compromised.

Privilege withdrawn


The certificate (public-key or attribute certificate) was revoked because a privilege contained within that certificate has been withdrawn.

No reason


The certificate is revoked without specification of a reason.

Certificate hold


The certificate is on hold, that is, temporarily invalid.


A certificate without any restrictions, such as revocation or on hold.

Revocation of CA certificates can only be performed using the Administration Workbench (AWB) as described in CA administration tasks in Certificate Manager.

Handle certificates on hold

Once a certificate hold has been issued, you can handle it in one of the following ways:

  • Let the certificate remain on the Certificate Revocation List (CRL) with no further action, causing users to reject transactions issued during the hold period.


  • Let the certificate be replaced by a (final) revocation for the same certificate, in which case the reason shall be one of the standard reasons for revocation. The revocation date shall be the date when the certificate was placed on hold.


  • Let the certificate be reinstated, that is, explicitly released and the entry removed from the CRL.

Additional information


JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.