Horizon 2.10.6 release notes

Fixed an issue where EST requests were rejected on decentralized profiles when the PKCS#10 contained a challengePassword attribute.

Fixed an issue where the Stream connector did not forward the template v2 extension value to Stream.

Fixed an issue where the Registration Authority and Dashboard sections were hidden after upgrading to 2.10 and required a page refresh.

Fixed a UI issue where asynchronous notifications were displayed as [Object, Object] on profile edit pages, preventing profiles from being saved.

Fixed an issue where the OTPKI connector did not forward RFC822 (email) SANs.

Fixed an issue where Stream enrollment failed when using X509 authentication.

Fixed an issue where certificates attached to a deactivated WebRA profile were still automatically renewed.

Fixed an issue where escrowed Microsoft private key enrollment failed due to incorrect msPrivateKeyHash serialization.

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