Revoke Certificate
venafi_tpp.revoke_certificate
ActionBusiness appsconnection required
Calls the Venafi TLS Protect Datacenter API with the connection's credentials.
Ask the issuing authority to revoke a certificate.
Connection
- Required
- Yes — the node will not save without one
- Auth type
- Custom
- Providers
- Venafi TLS Protect Datacenter
- Secret shape
- {"username": "…", "password": "…"} or {"access_token": "…"}
- Config it needs
- base_url, client_id, scope
- Resolved by
- config.connection_id, else node.connection_id
Configuration
6 fields, none required. A dotted path is a nested object and name[] an array of objects — the editor renders the same tree.
| Field | Type | Required | Default | Constraints | Example |
|---|---|---|---|---|---|
certificate_dn Distinguished Name of the certificate to revoke. | string | No | — | — | \VED\Policy\Certificates\www.acme.com |
thumbprint SHA-1 thumbprint of the certificate to revoke, when its DN is not known. | string | No | — | — | B2A9E0C4F6A1D3B5C7E9F1A3B5C7D9E1F3A5B7C9 |
reason Venafi's revocation reason code: 0 none, 1 user key compromised, 2 CA key compromised, 3 user changed affiliation, 4 certificate superseded, 5 original use no longer valid. | number | No | 0 | 0–5 | — |
comments Why the certificate is being revoked, recorded against the request. | string | No | — | — | Replaced during the September key rotation. |
disable Also disable the certificate object, so no replacement is enrolled. | boolean | No | false | — | — |
work_to_do_timeout Seconds to wait for the certificate authority before answering. Left at 0 the platform queues the work and answers straight away. | number | No | 0 | 0–120 | — |
- At least one of certificate_dn, thumbprint must be set.
Example configuration
Every value below is the contract’s own example or default — nothing invented.
{
"certificate_dn": "\\VED\\Policy\\Certificates\\www.acme.com",
"comments": "Replaced during the September key rotation.",
"disable": false,
"reason": 0,
"thumbprint": "B2A9E0C4F6A1D3B5C7E9F1A3B5C7D9E1F3A5B7C9",
"work_to_do_timeout": 0
}Output
One shape.
result
| Field | Type | Example |
|---|---|---|
Requested True when the revocation was submitted. | boolean | — |
Success True when the platform accepted the request. | boolean | — |
Revoked True when the certificate was already revoked. | boolean | — |
{
"Requested": false,
"Revoked": false,
"Success": false
}Notes
- Venafi answers 200 with Success false when it refuses a revocation; the node raises that as an error rather than reporting a success.
Related Venafi TLS Protect Datacenter nodes
See Revoke Certificate run in a workflow.
In a technical demo we add the Venafi TLS Protect Datacenter connection, drop the node on the canvas and let Workflow Health pre-flight it before the first real run.