Horizon 2.8.2 release notes

[HOR-357] - Third party data updates from discovery on managed certificates can now be enabled in profile configuration. Learn more…​

[HOR-604] - REST Notifications: REST requests can now be chained to allow complex request scenarios

[HOR-544] - Stream connector: Now supports Microsoft Template V2 extension

[HOR-644] - Modal windows no longer close when clicking outside

[HOR-525] - Magic link reports can now be stored on S3 Buckets using advanced configuration. Learn more…​

[HOR-635] - AWS Connector: certificate chain is now pushed in leaf to root order

[HOR-701] - Nexus connector: Fixed an issue where multi valued DN elements and IP SANs were not transmitted

[HOR-591] - Requests: Fixed a UI issue where teams could not be changed when using bulk validation

[HOR-518] - Requests: Fixed a UI issue where teams could not be searched using their display name when approving a request

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

[HOR-604] - REST notifications now require a sequence parameter containing the REST parameters for each request