See below the known issues in the Timestamping Authority solution distributed with PKI Hub 1.3.0 for Cryptographic Security Platform 1.2.0.

Large kmdata files not supported  (ATEAM-16338)

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

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 PKI Hub 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.

tsactl logs not forwarded to Splunk (EDM-13275)

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

See Browsing logs for how to browse logs with Grafana or a Splunk server.