Known Issues

This section describes the known issues in this release.

CERT

  • Re-enrollment support for GlobalSign MSSL is not available for the enrolled GlobalSign MSSL certificates.
  • When a custom attribute with the same name exists for different CAs, it is not being added to the custom attribute list, even though a message indicates that the custom attribute was successfully added.
  • When a custom attribute with the same name exists for different CAs, it is not being added to the custom attribute list, even though a message indicates that the custom attribute was successfully added.
  • The CA setting name is not mapped correctly for certificates uploaded or discovered from other sources when the issuer common name contains an apostrophe.
  • In Let’s Encrypt certificate enrollment, the HTTP flow method lacks proper configuration details when accessed through Policy Central.
  • The CA Attributes Sync Job log ordering is inconsistent at times.
  • Incorrect status displayed for revoked certificates in HashiCorp certificate discovery.
  • Entrust MPKI - Enroll fails with multiple common name.
  • HashiCorp Vault CA values are not populated on the Code Signing enrollment page.
  • ACME :: Dynamic EAB - Getting duplicate mail ids when importing the <.csv> file twice.

Managed K8s GKE Cluster

  • MSCA discovery is stuck in the queue during the persistence stage with API ID: cert-discovery-persist.
  • The migration was performed from v2024.0.0 FP3 to v2026.1.0.0. However, since the version was set to v2024.1.2, the relevant script was not executed, resulting in the Slack entry missing from the vendor list. This issue impacts only the Slack notification use case in the Policy Engine.