manage_acme_certificate_domain
Add or remove a single domain (SAN) validation entry on an ACME certificate so pfSense can prove ownership before issuance.
Instructions
Add or remove a domain (SAN) validation entry on an ACME certificate
Each ACME certificate needs at least one domain entry describing how pfSense proves ownership to Let's Encrypt (HTTP-01, DNS-01 via a provider API, manual DNS, etc.) before a certificate can be issued. This manages entries one at a time instead of replacing the whole a_domainlist array (see update_acme_certificate for a full-replace).
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"action": "<action>",
"parent_id": "<parent_id>"
},
"name": "manage_acme_certificate_domain"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | Fully-qualified domain name / SAN (required for create) | |
| action | Yes | Action to perform ('create' or 'delete') | |
| method | No | Validation method (required for create). Common values: 'dns_cf' (Cloudflare DNS-01), 'http' (HTTP-01), 'webroot'. See the pfSense ACME package for the full provider list. | |
| confirm | No | Must be set to True for delete operations. Safety gate for destructive operations. | |
| domain_id | No | Domain entry ID (required for delete) | |
| parent_id | Yes | ACME certificate ID (from search_acme_certificates) | |
| provider_fields | No | Method-specific credential/config fields, merged directly into the request. Example for method='dns_cf' with an API token: {"cf_token": "..."}. With a legacy global key: {"cf_email": "...", "cf_key": "..."}. | |
| apply_immediately | No | Whether to apply changes immediately |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||