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 531: POST Monitoring Revocation Input Parameters
Name | In | Description |
---|---|---|
Dashboard | Body |
Required. An object indicating the configuration for display on the dashboard. |
Body |
|
|
Encode As Plus Signs | Body | A Boolean indicating whether plus signs (“+”) in the Location URL for CRL endpoints should be encoded as plus signs (%2B), as might typically be required for a delta CRL, or encoded as spaces (%20) (true/false). |
Endpoint Type | Body | Required. A string indicating the type of revocation monitoring endpoint: OCSP or CRL. |
Id | Path | Required. An integer indicating the Keyfactor Command reference ID of the revocation monitoring location. |
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 plus, if your URL contains plus signs, you need to take special care and make sure that you select the correct value for the
For OCSP endpoints, this is the full URL to the OCSP responder servicing this certificate authority's CRL. |
Name | Body | Required. A string indicating the name of the revocation monitoring location. |
OCSP Parameters | Body |
|
Schedule | Body |
An object containing the inventory schedule set for the revocation monitoring location. |
Use Workflows | Body | A Boolean indicating whether the alert uses workflows to deliver the alerts (true) or the legacy alerting system (false). |
Table 532: POST Monitoring Revocation Response Data
Name | Description |
---|---|
Dashboard |
An object indicating the configuration for display on the dashboard. |
An object indicating the email recipients and reminder schedule for reminder alerts. |
|
Encode As Plus Signs | A Boolean indicating whether plus signs (“+”) in the Location URL for CRL endpoints should be encoded as plus signs (%2B), as might typically be required for a delta CRL, or encoded as spaces (%20) (true/false). |
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. |
Name | A string indicating the name of the revocation monitoring location. |
OCSP Parameters |
For OCSP endpoints only, an object indicating the OCSP endpoint configuration. |
Schedule |
An object containing the inventory schedule set for the revocation monitoring location. |
Use Workflows | A Boolean indicating whether the alert uses workflows to deliver the alerts (true) or the legacy alerting system (false). |
Workflow Enabled | A Boolean indicating whether the workflow used to deliver alerts for this revocation monitoring location is enabled (true) or not (false). |
Workflow Id | A string indicating the Keyfactor Command reference GUID of the workflow used to deliver alerts for this revocation monitoring location. |
Workflow Name | A string indicating the name of the workflow used to deliver alerts for this revocation monitoring location. |
Workflow Published Version | An integer indicating the published version of the workflow used to deliver alerts for this revocation monitoring location. |



Was this page helpful? Provide Feedback