Skip to main content

1.7.2

Released 11 Nov 2026

New​

  • Fortinet FortiGate distribution target. The certificate is created on the FortiGate once and updated in place on every renewal, so its name and every VIP, SSL inspection profile and SSL VPN that uses it keep working without dropping connections. The chain is served from the FortiGate's CA store: an intermediate it already holds is reused, and importing a missing one closes the TLS connections the FortiGate terminates that are open at that moment, once — the dry run names the VIPs this affects.
  • Optional bindings. A FortiGate target can add the certificate to firewall VIPs, to SSL inspection profiles in replace mode and to the SSL VPN; every deploy adds it where it is missing and nothing is ever removed.
  • Live pickers for FortiGate. The target form lists the FortiGate's certificates, VIPs and SSL inspection profiles, and marks a profile that cannot keep a server certificate.
  • Per-distribution FortiGate overrides. A distribution can pin the certificate name on one target or replace the target's bindings.
  • Group values in distribution overrides. A distribution's overrides now have a row for each target group of the module: its value applies to every member without its own value, targets added to the group later included, and a member's own value still wins. Two groups with a value cannot share a target — the save names the groups and the targets.
  • An overrides list that scales. The overrides drawer lists every target on one line with what it deploys as and where that value comes from (its own row, its group, the Default row, its own settings or the generated name), filters by source and by problems, and opens one target's editor at a time. Empty fields say what they inherit.
  • AD CS without CES/CEP. A Microsoft AD CS connection can now talk to the CA directly, so a server with only the Certification Authority role is enough: it needs TCP 445 to the CA server and signs in with Kerberos or NTLM using a normal domain account. Find CAs lists the forest's CAs from Active Directory, and the templates come from there too — or you type their names.
  • Templates checked before a request is sent. For these connections, a template that would build its subject from Active Directory, needs enrollment-agent signatures or does not let the account enroll is marked unusable with its reason, and a key type the template does not accept is refused before anything reaches the CA. The issue wizard also shows which templates need a CA manager's approval.

Fixed​

  • Fan-out batches use a group's credential. A target without its own credential took the default credential of its first target group on a normal run but none in a fan-out batch or a retry, so it failed there; every run now uses it.
  • A validation re-check no longer passes with nothing left to check. When no validation endpoint applied to a target any more by the time its re-check ran, the re-check reported success; the distribution now stays partial and the job log says to run it again.
  • Approval requests show removed override rows. A request that removed a target's overrides (or cleared them all) showed no difference; the reviewer now sees each removed row, and override rows are named by target or group instead of by id.
  • A cancelled distribution run keeps what it deployed. When a run was cancelled while it was deploying, the targets' record of what they now hold was dropped, so the next run started without it; it is now kept for every target type.
  • AD CS certificates that do not name the domain are refused. A template that builds its subject from Active Directory makes the CA issue a certificate naming the service account instead of the requested domain, and CertAutoPilot stored and distributed it. Such a certificate is now refused with MSCA_CERT_NAME_MISMATCH and the template fix — the certificate in use keeps serving and the request is not sent again. This also applies to renewals of certificates issued before: a certificate whose template builds its subject from Active Directory, or that names the domain only in its subject and not in its alternative names, now stops renewing until the template is fixed.
FortiGate API token and admin lockout

The target authenticates with a REST API administrator token. FortiGate counts refused tokens toward its admin lockout for the source address, so a refused token is never retried, the run sends nothing more to that FortiGate, and the same token is not sent to it again for about 70 seconds. Without TLS verification or a pinned fingerprint, the run warns that the token went to the firewall unverified. The least privilege is an admin profile with VPN read-write, plus Firewall → Address read-write for VIP bindings and Firewall → Others read-write for SSL inspection profiles.

Upgrade every node before saving group values

On a multi-node installation, a group value in a distribution's overrides is saved only once every node runs 1.7.2 — an older node would ignore it and deploy the Default row's value instead. Do not downgrade once group values are in use.

Upgrade every node before adding a FortiGate target

On a multi-node installation, a node still on an earlier release does not know the FortiGate target: a distribution run or health check it picks up fails with "module type fortigate not found". Finish the upgrade before creating FortiGate targets.

Upgrade every node before creating a direct AD CS connection

On a multi-node installation, a connection direct to the CA can be created only after every node runs 1.7.2 — until then it is refused, because an older node would not know how to use it. Existing CES/CEP connections keep working unchanged.