Per-distribution overrides
One target often serves many certificates. A distribution's overrides set, for that one certificate, what its target would otherwise decide: the object name on the device, where the certificate is placed (profiles, VIPs, Secrets, bindings…) and the validation endpoints. Nothing about the target itself changes.
Open them from a certificate: Distributions → ⋯ → Per-target overrides.
Where a value comes from
Each target takes its value from the most specific row that sets it:
- The target's own row.
- Its group's row — when the target is a member of one of the module's target groups that has a value.
- The Default row (all targets).
- The target's own settings.
- The generated name
cap-<token>-<domain>(for modules that name objects; MerlinCDN, IIS, Cloudflare and SSH/WinRM have none).
Group rows and the Default row also apply to targets added later — a target that joins the group gets the group's value unless it has its own.
How a row "sets" a value depends on the module, exactly as the deploy reads it:
| Module | What one row decides |
|---|---|
| F5 BIG-IP | Name and partition field by field; the profile list as a whole |
| NetScaler, Vault, AWS ACM, Azure Key Vault, Elchi, PAN-OS | The name field by field |
| FortiWeb | The name, the chain group, the SNI list and the multi-certificate list each on their own |
| FortiGate | The name (own row only); the placements as a whole |
| A10 Thunder | The name (own row only); templates and SNI entries, each as a whole |
| Huawei Cloud | The target's own row decides the whole object (name and id together); a group or Default row gives only a name |
| Kubernetes, MerlinCDN, SSH, WinRM | The first row that sets the module's part decides it whole |
| IIS | The placement from the first row that has one; the name check (verify_binding_names) on its own |
| Cloudflare | Take over / alongside / refuse from the first row that chooses; bundle, type and geo field by field |
| Validation endpoints (every module) | The first non-empty list, whole |
So a target row that sets only an F5 partition still takes its name from its group or the Default row.
"None" — clearing a list
For three lists the drawer offers three states: inherited (the next row, else the target, decides), None and Set here. They are the FortiGate placements and the A10 templates and SNI entries — the only override lists the server tells apart from "not set". None stores an explicit empty value: that row clears the list, so the certificate is added to no placement (FortiGate) or named in no template or SNI entry (A10) for this distribution, even when the target or a lower row has some. Emptying a list's tag box returns it to inherited; None is only chosen explicitly. Over the API None is an empty list ("templates": [], "sni": []) or an empty object ("placements": {}).
Group rows
A group row exists for every target group the module deploys to. In the drawer each group has a header that says what the group's value is, how many members it applies to and how many have their own value; Set group value / Edit group value opens it.
- A member's own value always wins over its group's.
- Members of a group with no value use the Default row.
- A target listed in the module directly that is also a member of a group counts as a member.
- A target is listed once, under the first of its groups (in the module's order); its other groups are named under it.
Two groups with a value
A target can take a value from one group only. When two of its groups both have a row that sets anything (a validation endpoint counts), the save is refused (422, OVERRIDE_GROUP_CONFLICT) and the message names both groups and the shared targets. Clear one of the two group values, or take the targets out of one group. The target's own row does not resolve it: a row that sets only part of the value would still take the rest from one of the groups.
If a target joins a second group after the save, the next run applies no group value to it — it uses its own row, the Default row, its own settings or the generated name — and its result carries the warning OVERRIDE_GROUP_CONFLICT. The drawer shows it in red, and the dry run warns before the run.
What a group or Default row cannot set
A value that names one object on one device is accepted on a target's own row only, because a group row and the Default row reach several devices (and targets added later):
- Cloudflare: the custom certificate to take over (
certificate_id). - FortiGate:
cert_nameandplacements.ssl_vpn. - A10 Thunder:
cert_name. - Huawei Cloud:
certificate_id,domain_id,domain_name.
Two checks that need one target are skipped on a group row as on the Default row and happen at deploy instead: an IIS single-binding placement without a site on a target that covers several sites, and the cPanel whm_user mode.
Live pickers are off on group rows and on the Default row — their members can be different devices — so values are typed. MerlinCDN is the exception when every member of the group uses the same credential and host.
The list
The drawer lists every target in one line: its host, what it deploys as, where that comes from (Own, Group: …, Default, Target's setting, Generated, or Mixed when the target's row sets only part of it), how many validation endpoints apply, and whether it needs a fix. Click a line (or press Enter) to edit that target; one editor is open at a time. Filters above the list show only the targets with their own value, from a group, from the Default row, from their own settings, those that need a fix and those with a group conflict. Selecting targets lets you clear their own values in one step — to give several targets one value, use their group or the Default row.
Saving, approvals and upgrades
- Saving replaces the whole override set. Rows of targets or groups the module no longer deploys to are dropped on save.
- With distribution approval on, an operator's change becomes a request; the reviewer sees each changed row by name (target, group or Default row), including rows the change removes.
- Group rows are saved only once every node of the cluster runs a version that applies them (409
CLUSTER_UPGRADE_REQUIREDuntil then). An approved request refused this way can be retried after the upgrade. - A fan-out batch reads group membership when it runs, like the rest of the target list.
Video tutorials
Short, hands-on videos showing this feature working for real. English audio, English and Turkish subtitles. All video tutorials →