DELETE Certificates
The DELETE /Certificates operation deletes multiple certificates from Keyfactor Command in a single request. If the specified certificates have associated private keys stored in the database, these private keys are also removed. On success, the operation returns 204 with no content. IDs of any certificates that could not be deleted are returned in the response body. Delete operations will continue until the entire array of IDs has been processed.
Whenever a certificate that is part of a certificate renewal chain is deleted, the certificates on either end of the deleted certificate will have their certificate histories updated. The update will reflect the deletion of the certificate in the renewal chain, showing either the certificate before or after the deleted certificate.
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 304: DELETE Certificates Input Parameters
| Name | In | Description |
|---|---|---|
| n/a | Body | Required. A JSON array of integers containing the Keyfactor Command certificate IDs for certificates that should be deleted in the form: [123,789,567] Use the GET Certificates operation to determine the certificate IDs. The input is not a structured object and does not include field names. |
| 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:
Use either ContainerId or CollectionId, not both. See Certificate Collection Permissions for more information. |
Was this page helpful? Provide Feedback