[4.1] Patch - Sept 30, 2021

Fortanix Data Security Manager (DSM) 4.1 Patch (4.1.1499) comes with some improvements and provides an overview of resolved issues.

  • It is “REQUIRED” to upgrade Fortanix DSM to version 4.0 before upgrading to version 4.1 Patch (4.1.1499).
  • After the software package is uploaded, the expected time to upgrade a 3-node cluster is about 1 hour.

1. Bug Fixes

  • Fixed an error where two key versions are created with a different name after copying a key from a Fortanix DSM group to an Azure group followed by rotating the key in the source group with linked key rotation. (JIRA: PROD-3677)
  • Fixed an issue that causing problems loading plugin page, when access to plugin GitHub was blocked through a firewall. (JIRA: ROFR-2795)
  • Resolved Cassandra crash due to stale hints file. (JIRA: DEVOPS-1779)

2. Improvements

  • Added TCP keepalive to detect stale network connections in the backend. (JIRA: PROD-3673)
  • Implemented timeout and retry for pushing audit logs to Cassandra. (JIRA: PROD-3662)
  • Exclude audit log from repair job which causes problems in Cassandra stability during the Cassandra compaction for audit log tables. (JIRA: DEVOPS-1728)

3. Known Issues

  • The Fortanix DSM UI fails to accept a valid certificate during Splunk configuration on the system administrator account. As a workaround, if Splunk TLS configuration is required, then the Fortanix DSM API can be directly called to configure the same. (JIRA: ROFR-2581)
  • When doing operations such as scan on groups linked to Azure Key Vault, you may receive a “not enough memory” error when the key vault has more than 100 keys. (JIRA: PROD -3568)

4. Installation

To download the DSM SGX (on-prem/Azure) and Software (AWS/Azure/VMWare) packages, click here.


Please sign in to leave a comment.

Was this article helpful?
0 out of 0 found this helpful