Horizon 2.10.2 release notes
Here are the release notes for EverTrust Horizon v2.10.2, released on 2026-06-25.
For the installation and upgrade procedure, please refer to the Installation and Upgrade guide.
3. Bug Fixes
-
Fixed an issue where certificates could not be enrolled or renewed with a Nexus CM PKI
-
Fixed an issue where renewal requests could not be opened when they were created through the API without using the
moduleproperty -
Fixed an issue where event analytics synchronization could fail
-
Fixed a UI issue where the Extensions card overflowed horizontally when displaying long values in the Crypto Decoder
-
Fixed a UI issue where action buttons were missing from the Search Certificates page
-
Fixed a UI issue where the "Key Usages" card was missing from the certificate "More Details" page
-
Fixed a UI issue where asynchronous notifications were not properly displayed on the Edit SCEP Profile page
-
Fixed a UI issue where the status of a policy was not displayed on the DCV Lifecycle page
-
Fixed a UI issue where the Netscaler category was not displayed in the side navigation
4. Known Defects
-
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