Horizon 2.8.1 release notes

Here are the release notes for EverTrust Horizon v2.8.1, released on 2026-01-09.

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

1. New Features

[None]

2. Enhancements

  • [HOR-108] - Microsoft template v2 extensions are now supported when using the WCCE protocol (PKI support may vary)

  • [HOR-207] - Enables WebRA profiles for automation policies

  • [HOR-239] - ACME Connector: HMAC algorithm can now be specified manually when necessary

  • [HOR-235] - Nameshield Connector: Added custom data mapping

  • [HOR-129] - Dashboards can now be exported as PNG files from the dashboard page

3. Bug Fixes

  • [HOR-188] - Fixed an issue where notifications would not retry automatically and could not be retried manually

  • [HOR-160] - Fixed an issue where SANs deleted at the validation step would still be included in the final request

  • [HOR-230] - Fixed an issue where the Mongo lease would not function correctly when using TLS authentication to the Mongo database

  • [HOR-222] - Fixed an issue where long literals in HQL queries were not correctly handled

  • [HOR-589] - Fixed an issue where pagination was not displayed on the Monitored profiles page

  • [HOR-354] - Fixed an issue where certificate attachments could not be added to certificate import notifications

  • [HOR-220] - Fixed an issue where OIDC connectors would not use Horizon’s trusted CAs

  • [HOR-156] - Fixed an issue where long requests would not be entirely visible in report configuration

  • [HOR-473] - Fixed an issue where CSRs with non-RFC-compliant extensions were rejected

  • [HOR-124] - Fixed an issue where the renew_api permission would not allow searching for certificates to renew

  • [HOR-123] - Fixed an issue where the crlLifetime parameter was not saved in the Integrated connector

4. Known Defects

  • Due to a misconfiguration, CRL synchronization could stop updating and remain out of date. To fix this, add the following line to the added in the extra configuration: crl-task-dispatcher.thread-pool-executor.fixed-pool-size = 7. This issue has been resolved in 2.8.7

  • 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.8.9

5. API modifications

[None]