Horizon 2.10.1 release notes

Here are the release notes for EverTrust Horizon v2.10.1, released on 2026-06-17.

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 the license count was not displayed correctly for legacy licenses

  • Fixed an issue where disabling a DCV policy did not cancel its scheduled execution

  • Fixed an issue where the "Follow criteria" action on the events page did not behave as expected

4. Known Defects

  • In rare cases, a new event can be inserted without the required synchronization data, which prevents the event analytics database from synchronizing and thus responding to any further requests. This issue has been resolved in 2.10.2

  • Certificate revocation through the DigiCert connector fails to complete. This issue has been resolved in 2.10.3

  • Enrollment requests through the Sectigo connector fail to complete. This issue has been resolved in 2.10.4

  • 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]