Horizon 2.8.3 release notes

Here are the release notes for EverTrust Horizon v2.8.3, released on 2026-02-23.

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

1. New Features

[None]

2. Enhancements

  • [HOR-157] - The certificate SANs are now displayed on revocation requests

3. Bug Fixes

  • [HOR-820] - Fixed an issue where LDAP sockets created by the LDAP datasource were not properly closed

  • [HOR-736] - Fixed an issue where anonymous requests could not be approved

  • [HOR-764] - Fixed an issue where request approvals were blocked on enroll requests for users with label permissions

  • [HOR-791] - Fixed an issue where proxy was not used for certain calls in the OIDC authentication flow

  • [HOR-755] - Fixed an issue where 0-length password policies could be saved

  • [HOR-852] - Fixed a UI issue where reports containing an empty body could not be edited

  • [HOR-817] - Fixed a UI issue where discovery permissions could not be saved

  • [HOR-814] - Fixed a UI issue where data sources were not available in the computation rule helper on certificate profiles in certain conditions

  • [HOR-802] - Fixed a UI issue where a certificate could not be accessed using its ID

  • [HOR-722] - Fixed a UI issue where a request could not be accessed using its ID

  • [HOR-800] - Fixed a UI issue where Enrollment Agent Credentials edits were not saved on the ADCS connector

  • [HOR-789] - Fixed inconsistent display of discovery panel in the More details certificate page

  • [HOR-784] - Fixed a UI issue where selection bugs occurred on the export workflow

  • [HOR-780] - Fixed a UI issue where filters could not be updated on the roles page

  • [HOR-766] - Fixed a UI issue where SCEP authorized challenge could not be generated in SCEP profiles

  • [HOR-742] - Fixed a UI issue where multi requests REST notifications behaved improperly when deleting a request

  • [HOR-728] - Fixed a UI issue where a role could not be created using the Administrator template

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]