Horizon 2.10.4 release notes

Here are the release notes for EverTrust Horizon v2.10.4, released on 2026-07-21.

For the installation and upgrade procedure, please refer to the Installation and Upgrade guide.

1. New Features

[None]

2. Enhancements

[None]

3. Bug Fixes

  • Fixed an issue where certificate enrollment on a Sectigo PKI connector failed with a metadata error.

  • Fixed an issue where a PKCS#12 delivered through a REST notification ignored the WebRA profile’s store encryption type.

  • Fixed an issue where announcements were sometimes not displayed for users without permissions or not logged in.

  • Fixed a UI issue where the "Disable auto renewal" confirmation dialog was triggered on profile creation.

  • Fixed an issue where a CertEurope PKI connector could not be saved when the validDays field was not set.

  • Fixed an issue where a Sectigo PKI connector could not be added or edited when the retryInterval field was not set.

  • Fixed a UI issue where the Auditor role preset did not grant read permissions on the DCV module.

  • Fixed an issue where the Discovery feed returned a 500 error when a discovered certificate referenced a disabled certificate profile.

  • Fixed an issue where the DCV menu threw an error when a DigiCert account had no domains.

4. Known Defects

  • Stream connector does not forward the value of the MS Template V2 extension. This issue has been resolved in 2.10.6

  • Stream connector fails to enroll when using certificate authentication. This issue has been resolved in 2.10.6

  • Stream connector fails to enroll when using WCCE Escrow mode. This issue has been resolved in 2.10.6

  • OTPKI connector does not set values for the RFC822Name (email) SAN, resulting in certificates where this field is missing. This issue has been resolved in 2.10.6

  • The PKI connector healthcheck does not report connection errors, resulting in unreachable or misconfigured connectors being wrongly reported as healthy. This issue has been resolved in 2.10.8

  • Nameshield reissue can sometimes return the certificate value from before the reissue. This issue has been resolved in 2.10.8

  • Revocation triggers are run before enrollment triggers when the maximum number of certificates per holder is reached (revoked mode). When this number is 1, this can cause deployment issues on renewals. This issue has been resolved in 2.10.9

  • Saving an API Token credential in the UI replaces its value with a placeholder, even when the value is not edited. This issue has been resolved in 2.10.9

  • Renewal requests through the Sectigo connector return the same certificate. This issue has been resolved in 2.10.10

5. API modifications

[None]