Known Limitations
This section describes the known limitations in software in this release.
CLM
- In IP range and subnet discovery, cipher suite results are incomplete for an endpoint that requires a post-quantum TLS handshake. Discovery can show the certificate and still report zero protocols and cipher suites, and the message can look like a TLS protocol failure. Cipher enumeration depends on a third-party library that cannot complete a post-quantum key exchange, and this will be revisited when that library adds the support.
- In Policy Engine, a re-enrollment template can be saved when a selected CSR generation source, such as HSM, does not have its own key type and dependent fields configured. Key Type, Hash Function, and Bit Length are optional on the re-enrollment template, so that check is skipped and the incomplete template is accepted. The template is stored without those values, and during re-enrollment the key type, hash function, and bit length for that CSR source are missing on the form, or the re-enrollment can fail with an error.
- Renew, reissue, or any other CLM action fails with a policy non-compliance error when the issuing CA signs the certificate with a hash algorithm, such as SHAKE256, that is not selected on the certificate policy. Select that algorithm on the policy when it is available and the CA account uses it. For certificate authorities where the post-quantum hash is not yet offered in CA policy, this remains a limitation until that support is added.
- DigiCert scheduled discovery filtered by Certificate Issue Date can return certificates whose validity starts before the selected range. AppViewX sends that range as the DigiCert order-created date, and DigiCert can return an order created in range whose certificate validity starts earlier.
- During certificate re-enrollment, if no matching CA-specific template is found, the request falls back to the default re-enrollment template. In this case, the bit length field remains blank for PQC certificates because the default template does not contain the corresponding post-quantum algorithm values.
- After a certificate is issued with SLH-DSA, the Key Version selected at issuance is not shown when you view or edit the CA connector. This applies to every supported certificate authority, and CSR submission for SLH-DSA can fail because that value is unavailable.
- Policies configured with Azure Premium Key Vault endpoints are not eligible for migration.
Platform
- While performing multiple delete operations across different pages, only the last selected item is deleted. The other selected items are not deleted.
- As part of the security updates, the TACACS+ data decryption algorithm has been
upgraded to SHA-256. To maintain compatibility with data encrypted using the
previous MD5 algorithm, set the following classpath variable:
-DTACACS_HASH_ALGORITHM=MD5
