Skip to main content

1.7.4

Released 16 Nov 2026

New​

  • New release notice on CertAutoPilot OS. Org owners and admins see x.y.z ready beside the version at the top of the sidebar when a newer release can be installed; pointing at it shows the console command (system app update x.y.z) and a link to the release notes. The appliance checks the release list once a day and shows nothing when it cannot reach it; other install types are not checked.
  • Minimum access in every module guide. Each distribution module guide opens its permissions section with the exact role or rights to give the target account, what only an optional setting needs, what is not needed, and a ready-to-use definition (IAM policy, Kubernetes Role, CLI commands). A separate table lists who may do what inside CertAutoPilot.

Improved​

  • Access is its own card. On the edit pages of targets, modules, credentials, path sets, action sets, secret stores, DNS credentials, ACME accounts and CA connections, Access now sits in its own card below the form instead of under the form's Update button, because it is saved on its own.
  • GlobalSign: Check now. Asking for a domain-validation check no longer uses up one of the scheduled checks or pushes the next scheduled check later.
  • GlobalSign: issued certificates. The connection's list of issued certificates is read from GlobalSign once a minute and shown from that read when you open it again; Refresh reads it again.
  • GlobalSign: slow answers. The account view, domain validations, the issued-certificate list, the connection test and the approval e-mail calls wait for GlobalSign's answer instead of showing an error after 30 seconds.
  • CA connector certificates: clearer page. The certificate page names how the domain was validated (for example E-mail approval) instead of Vendor DCV, shows Account policy instead of an internal product code for a vendor without products, and the timeline records when the approval e-mail was sent and when the vendor validated the domain, and names a rekey as a rekey. Event details are shown as readable text.
  • Renew by hand. With auto-renew off, the validity bar and Next Renewal say Renew by hand from the date instead of suggesting an automatic renewal.
  • GlobalSign: revoke during a validation. While a renewal or re-issue waits for its domain validation, the refusal to revoke says to stop the validation first, and the order card says so too.

Changed behaviour​

  • CertAutoPilot OS contacts ghcr.io once a day for the new release notice. Nothing about the installation is sent.
  • Expiring counts follow each certificate's lifetime. The dashboard's and header's Expiring counts, the scheduled PDF report's expiry columns and expiring list, the risk score's expiry factors and the chain view's expiry badge count a certificate as expiring within 30 days or in the last third of its life, whichever is shorter — a freshly issued 30-day certificate is no longer shown as expiring and rated high risk. The links open the list with the matching new expiring_within filter; expires_in_days stays a calendar window.
  • CA connectors: renewal threshold below the certificate's validity. A renewal threshold at or above the longest validity the account's policy grants (for example 30 days on an account that issues 30-day certificates) is refused with CA_RENEWAL_THRESHOLD_TOO_LONG; such a threshold renewed every certificate halfway through its life and ordered twice as many. The issue wizard suggests a third of the validity (at most 90 days), and a certificate created through the API without a threshold gets the same value when the organisation default would be too long.
  • GlobalSign: extended key usage. When the account policy lets the request choose the extended key usage, CertAutoPilot now asks for TLS server authentication; each pattern of the policy must match the whole usage. When the policy makes usages optional and does not list TLS server authentication, nothing is sent and GlobalSign applies its default. A policy that requires a usage other than TLS server authentication, or more than one usage, is refused with POLICY_MISMATCH before anything is ordered.

Fixed​

  • What Renew and Re-issue do. ACME and AD CS certificates now have the same ⓘ explanation next to the actions that CA connector certificates have: the key, the validation and what happens to the current certificate.
  • Key rotation notice. A certificate set to make a new key on every renewal no longer shows Key rotation threshold reached for its whole life; the notice now reads Next renewal makes a new key and appears only before the renewal that rotates.
  • Chain choice follows the key type. The issue wizard's Chain offered by the CA list and a certificate's chain tab now list only chains the CA offered for the same key algorithm (RSA or ECDSA); an RSA certificate no longer offers a chain such as ISRG Root X2 that the CA gives ECDSA keys only.
  • Serial numbers keep their leading zero. A certificate's serial is shown in whole bytes, as the CA and other tools print it (01719E…, not 1719E…), on the certificate page, in the history and in the CSV export.
  • A10 Thunder: renaming a certificate back to a name it used before no longer fails with A10_CONFLICT; the file under that name is updated in place.
  • GlobalSign: saving a connection right after Generate CSR could drop the new pending key. Such a save is now refused with CA_CONNECTION_CHANGED; save again.
  • GlobalSign: saving a connection no longer undoes a status that a connection check set at the same moment.
  • GlobalSign: a renewal that waited for domain validation and made a new key now counts the key rotation even when its order step was interrupted.