Fortanix Data Security Manager (DSM) 4.4.2047 provides an overview of the resolved issues.
WARNING
It is “REQUIRED” to upgrade Fortanix DSM to version 4.2 or 4.3 before upgrading to version 4.4.2047. If you want to upgrade to 4.4.2047 from an older version, please reach out to the Fortanix Customer Success team
NOTE
After the software package is uploaded, the expected time to upgrade a 3-node cluster is about 1.5 to 2 hours from version 4.2 or 4.3 to 4.4.2047.
1. Bug Fixes
- Fixed a select account failure when the user selects an account that has a group backed by external DSM, where the group configuration involves some bad configuration values. This was caused by a backward compatibility issue when reading group configuration. (JIRA: PROD-4482).
2. Known Issues
- An account could be lost if account tables are inconsistent between nodes. Make sure a backup is successful before proceeding with ANY upgrade (JIRA: PROD-4234).
- When a node is removed from a 3-node cluster with build 4.2.2087, and the 2-node cluster is upgraded with build 4.3.xxxx, it is possible that the deploy job is exited and marked completed before cluster upgrade (JIRA: DEVOPS-2068). Workaround: If all the pods are healthy, you can deploy the version again.
- The sync key API returns “400 status code and response error” due to the short-term access token expiry during the sync key operation of a group linked to AWS KMS (JIRA: PROD-3903).
excludedoes not work in the proxy config for operations such as attestation (JIRA: PROD: 3311).
3. Installation
To download the DSM SGX (on-prem/Azure) and Software (AWS/Azure/VMWare) packages, click here.
Comments
Please sign in to leave a comment.