The Timestamping Authority solution has the following known issues.

This Timestamping Authority release focuses on dependency updates, not adding features or fixing bugs.

tsactl logs not forwarded to Splunk (EDM-13275)

When integrated with a Splunk server, Cryptographic Security Platform does not forward logs recording tsactl commands. However, these logs can be browsed using the Grafana portal.

See Managing Log Forwarder for integrating a Splunk server or Browsing logs with Grafana for browsing logs in the Grafana portal.

False alerts of failed deployment (ATEAM-16344) 

After a successful TimeStamping Authority deployment, the Management Console may occasionally display an error message that misleads the user into believing the deployment has failed.

Workaround:

  1. Log in to any of the Cryptographic Security Platform installation nodes.
  2. Run the following command line. 
    sudo kubectl get pods -n tsa
  3. Verify the TimeStamping Authority pods are running, in which case the deployment has been successful.

Large kmdata files not supported  (ATEAM-16338)

The tsactl import-nshield command does not support kmdata files larger than ~100KB.