This release of the Certificate Authority solution has the following known issues.
- Datadog errors in logs (ATEAM-17270)
- CA identifier uniqueness not enforced (ATEAM-17301)
- Some failed deployments appear as successful (ATEAM-17321)
- Cannot remove issuing CAs after removing the root CA (ATEAM-17445)
- HSM configuration requires an RFS server (ATEAM-17470)
- No error message when losing the database connection (ATEAM-17478)
Datadog errors in logs (ATEAM-17270)
The Certificate Authority logs include errors of the Datadog metrics tracker.
See Browsing logs with Grafana for how to browse logs.
CA identifier uniqueness not enforced (ATEAM-17301)
The Certificate Authorities solution allows reusing CA identifiers in the CA-creation form.
Removing a CA results in removing all CAs with the same identifier.
Some failed deployments appear as successful (ATEAM-17321)
Some Certificate Authorities deployments resulting in errors and non-running pods may appear as "successful" in the Management Console.
Cannot remove issuing CAs after removing the root CA (ATEAM-17445)
Certificate Authorities do not support removing issuing CAs that are subordinate to a root CA already removed.
HSM configuration requires an RFS server (ATEAM-17470)
Configuring an HSM (Hardware Security Module) for the Certificate Authorities solution requires access to a remote file system for nShield instead of simply uploading the kmdata TAR file.
No error message when losing the database connection (ATEAM-17478)
When losing the connection with the database, the Management Console displays no error message and allows clicking the Create Organization button.