Horizon 2.10.3 release notes
Here are the release notes for EverTrust Horizon v2.10.3, released on 2026-07-06.
For the installation and upgrade procedure, please refer to the Installation and Upgrade guide.
3. Bug Fixes
-
Fixed an issue where products were not listed when creating a SwissSign connector
-
Fixed an issue where revocation requests failed when using the DigiCert connector
-
Fixed an issue where the "My certificates" query was incorrect for users belonging to a team
-
Fixed an issue where the dynamic attributes available in the reset password page were incorrect
-
Fixed an issue where the reset password page was not accessible when resetting a local account password
-
Fixed a UI issue where revoking a single certificate reloaded the page and reset the search parameters
-
Fixed an issue where only the first letter of a label was taken into account in certificate aggregation results when using the analytics database
-
Fixed an issue where the license usage notification was never sent for the root tenant in multi-tenant instances
-
Fixed an issue where the license expiration date in notifications was incorrect for tenants in multi-tenant instances
-
Fixed an issue where creating a Service Account returned 200 instead of 201
4. Known Defects
-
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