DELETE Certificates Exclude
The DELETE /Certificates/Exclude method is used to delete and exclude a group of certificates from Keyfactor Command that match the list of IDs provided in the body.This endpoint An endpoint is a URL that enables the API to gain access to resources on a server. returns 204 with no content upon success.
Excluded certificates are certificates which have been removed from the main tables of the Keyfactor Command database and excluded from all Keyfactor Command functionality. These certificates will be 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 configured at multiple levels. You can apply them system-wide—for all certificates—or use fine-grained control by assigning permissions at the certificate collection The certificate search function allows you to query the Keyfactor Command database for certificates from any available source based on any criteria of the certificates and save the results as a collection that will be availble in other places in the Management Portal (e.g. expiration alerts and certain reports). level. The appropriate level depends on how the certificates are accessed. See Certificate Collection Permissions for more information about system-wide versus more targeted permission models.
Table 329: DELETE Certificates Exclude Input Parameters
Name | In | Description |
---|---|---|
ids | Body | Required. An array of integers containing the Keyfactor Command certificate IDs for certificates that should be deleted and excluded in the form: [123,789,567] Use the GET /Certificates method (see GET Certificates) 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 containers. 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. If both are specified, CollectionId takes precedence, and the ContainerId is ignored (defaults to 0). See Certificate Collection Permissions for more information. |



Was this page helpful? Provide Feedback