[4.8] Patch - July 21, 2022

Fortanix Data Security Manager (DSM) 4.8 patch release provides an overview of the resolved issues.

NOTE

4.8 patch release includes version 4.8.2075 for SGX and 4.8.2077 for non-SGX.

WARNING

It is “REQUIRED” to upgrade Fortanix DSM to version 4.4 or 4.6 before upgrading to the 4.8 patch version. If you want to upgrade to the 4.8 patch version from an older version, please reach out to the Fortanix Customer Success team.

1. Bug Fixes

• Fixed an issue that prevented admin apps from enabling/disabling mandatory multi-factor authentication at the account level. (JIRA: PROD-5049).

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).
• exclude does not work in the proxy config for operations such as attestation (JIRA: PROD: 3311).

4. Installation

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