Fortanix Data Security Manager (DSM) 4.16.2197 release provides an overview of improvements and resolved issues.
Updated the email re-verification cutoff date in the DSM email verification banner (JIRA: ROFR-4051).
The email re-verification cutoff date in the email verification banner is updated to May 12th, 2023.
2. Bug Fixes
- Fixed an issue where even though the “Use different output datatype” option is not enabled for DSM custom tokenization; the input data is tokenized to a different data type for the output token in the DSM UI (JIRA: ROFR-4052).
3. Known Issues
- 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).
- Unable to create an app when a Custom Group Role has the Create Apps permission enabled (JIRA: PROD-5764).
For a complete list of new features, enhancements to existing features, other improvements, and bug fixes refer to the full description of the 4.16 DSM on-prem and SaaS release.
To download the DSM SGX (on-prem/Azure) and Software (AWS/Azure/VMWare) packages, click here.
Please sign in to leave a comment.