POST Monitoring Revocation

The POST /Monitoring/Revocation method is used to add a revocation monitoring location. This method returns HTTP 200 OK on a success with details of the location.

Tip:  The following permissions (see Security Roles and Claims) are required to use this feature:

/monitoring/alerts/modify/

Table 473: POST Monitoring Revocation Input Parameters

Name In Description
Id Path Required. An integer indicating the Keyfactor Command reference ID of the revocation monitoring location.
Name Body Required. A string indicating the name of the revocation monitoring location.
Endpoint Type Body Required. A string indicating the type of revocation monitoring endpoint: OCSP or CRL.
Location Body

Required. A string indicating the location for the revocation monitoring endpoint.

For CRL endpoints, this can be either an HTTP location or an LDAP location. Be sure to monitor the CRL locations that are in use by applications in your environment—if you're monitoring LDAP locations but applications are using an HTTP location, you're not going to receive any warning if a CRL fails to publish to the HTTP location.

Important:  Because a “+” (plus sign) in a URL can represent either a space or a “+” Keyfactor Command has chosen to read “+” as a space. For CRL URLs that require a “+” (plus sign), rather than a space, replace plus signs in your CRL's URL with “%2B”. Only replace the plus signs you don't wish to be treated as a space.

For OCSP endpoints, this is the full URL to the OCSP responder servicing this certificate authority's CRL.

Email Body

Required*. for CRL endpoints. An object indicating the email recipients and reminder schedule for reminder alerts. ClosedShow email reminder details.

Dashboard Body

Required. An object indicating the configuration for display on the dashboard. ClosedShow dashboard details.

Schedule Body

An object containing the inventory schedule set for the revocation monitoring location. ClosedShow schedule details.

OCSP Parameters Body

Required*. for OCSP endpoints. For OCSP endpoints only, an object indicating the OCSP endpoint configuration. ClosedShow OCSP endpoint details.

Table 474: POST Monitoring Revocation Response Data

Name Description
Name A string indicating the name of the revocation monitoring location.
Endpoint Type A string indicating the type of revocation monitoring endpoint: OCSP or CRL.
Location

A string indicating the location for the revocation monitoring endpoint.

For CRL endpoints, this can be either an HTTP location or an LDAP location. Be sure to monitor the CRL locations that are in use by applications in your environment—if you're monitoring LDAP locations but applications are using an HTTP location, you're not going to receive any warning if a CRL fails to publish to the HTTP location.

For OCSP endpoints, this is the full URL to the OCSP responder servicing this certificate authority's CRL.

Email

An object indicating the email recipients and reminder schedule for reminder alerts. ClosedShow email reminder details.

Dashboard

An object indicating the configuration for display on the dashboard. ClosedShow dashboard details.

Schedule

An object containing the inventory schedule set for the revocation monitoring location. ClosedShow schedule details.

OCSP Parameters

For OCSP endpoints only, an object indicating the OCSP endpoint configuration. ClosedShow OCSP endpoint details.

Tip:  See the Keyfactor API Reference and Utility which provides a utility through which the Keyfactor APIClosed A set of functions to allow creation of applications. Keyfactor offers the Keyfactor API, which allows third-party software to integrate with the advanced certificate enrollment and management features of Keyfactor Command. endpoints can be called and results returned. It is intended to be used primarily for validation, testing and workflowClosed A workflow is a series of steps necessary to complete a process. In the context of Keyfactor Command, it refers to the workflow builder, which allows you automate event-driven tasks when a certificate is requested or revoked. development. It also serves secondarily as documentation for the API. The link to the Keyfactor API Reference and Utility is in the dropdown from the help icon () at the top of the Management Portal page next to the Log Out button.