DELETE Certificates ID

The DELETE /Certificates/{id} operation deletes an existing certificate with the specified ID from Keyfactor Command. If the specified certificate has an associated private keyClosed Private keys are used in cryptography (symmetric and asymmetric) to encrypt or sign content. In asymmetric cryptography, they are used together in a key pair with a public key. The private or secret key is retained by the key's creator, making it highly secure. stored in Keyfactor Command, this private key is also removed. On success, the operation returns 204 with no content.

Tip:  The following permissions (see Security Roles and Claims) are required to use this feature:
/certificates/collections/delete/
OR
/certificates/collections/delete/#/
OR
/certificates/collections/delete_and_exclude/
OR
/certificates/collections/delete_and_exclude/#/

Permissions for certificates can be set at the system-wide or resource-specific level. The appropriate level depends on how the certificates are accessed. See Certificate Collection Permissions for more information.

In permission strings, # represents a specific resource identifier. In /certificates/collections/ permission strings it refers to a certificate collection ID (for example, CollectionId) and in /certificate_stores/ permission strings it refers to a certificate store application ID (for example, containerId).

Table 305: DELETE Certificates {id} Input Parameters

Name In Description
id Path Required. The Keyfactor Command reference ID of the certificate to delete.

Use the GET Certificates operation to retrieve a list of certificates based on entered search criteria to determine the certificate ID. This information is also available in the certificate details for a certificate in the Keyfactor Command Management Portal.

CollectionId Query

An optional integer that specifies the certificate collection (CollectionId) to validate whether the user has sufficient permissions to perform the action. If a CollectionId is not provided, the user must have appropriate permissions granted system-wide or via certificate store applications.

Providing a CollectionId allows the system to check the user's permissions at the certificate collection level. Permissions are evaluated in the following order:

  1. System-wide certificate permissions
  2. Granular certificate permissions

Use either ContainerId or CollectionId, not both. If both are specified, CollectionId takes precedence, and the ContainerId is ignored (defaults to 0).

See Certificate Collection Permissions for more information.