DELETE Certificates Exclude ID
The DELETE /Certificates/Exclude/{id} operation deletes and excludes an existing certificate with the specified ID from the Keyfactor Command database. If the specified certificate has an associated private key
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 the database, this private key is also removed and cannot be restored.
On success, the operation returns 204 with no content.
Excluded certificates are removed from active use in Keyfactor Command and are no longer included in standard operations. These certificates are skipped and not re-imported during a CA
A certificate authority (CA) is an entity that issues digital certificates. Within Keyfactor Command, a CA may be a Microsoft CA or a Keyfactor gateway to a cloud-based or remote CA. synchronization or manual import
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 307: DELETE Certificates Exclude {id} Input Parameters
| Name | In | Description |
|---|---|---|
| ids | Body |
Required. The Keyfactor Command reference ID of the certificate to delete with exclusion. Use the GET Certificates operation to determine the certificate IDs. |
| 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