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.
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. |
Body |
|
|
Dashboard | Body |
Required. An object indicating the configuration for display on the dashboard. |
Schedule | Body |
An object containing the inventory schedule set for the revocation monitoring location. |
OCSP Parameters | Body |
|
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. |
An object indicating the email recipients and reminder schedule for reminder alerts. |
|
Dashboard |
An object indicating the configuration for display on the dashboard. |
Schedule |
An object containing the inventory schedule set for the revocation monitoring location. |
OCSP Parameters |
For OCSP endpoints only, an object indicating the OCSP endpoint configuration. |


