---
title: "[4.28] - May 28, 2024"
slug: "4-28-may-28-2024"
updated: 2026-08-19T06:33:58Z
published: 2026-08-19T06:33:58Z
canonical: "support.fortanix.com/4-28-may-28-2024"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://support.fortanix.com/llms.txt
> Use this file to discover all available pages before exploring further.

# [4.28] - May 28, 2024

Fortanix Data Security Manager (DSM) SaaS 4.28 comes with some exciting new enhancements and resolved issues.

> [!NOTE]
> NOTE
> 
> This release is for **SaaS only** and is not available for on-premises installations. Updates in this release will be part of a future on-premises release.

## 1. Enhancements to Existing Features

- **Removed the Transparent Encryption Proxy (TEP) wizard from the Integrations tab on Fortanix DSM. (JIRA: ROFR-4795).**

![2.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/26219736943508)

**Figure 1: Removed TEP Wizard**

## 2. DSM Accelerator Improvements and Bug Fixes

- **DSM Accelerator JCE Provider**:
  - Added support for Thin Jar bundled distribution in DSM Accelerator JCE Provider (**JIRA: PM-236**). *For more details, refer to the* [*DSM JCE Client Downloads*](/v1/docs/dsm-accelerator-downloads-dsm-accelerator-jce-provider)*.*
  - Added local cache export support in DSM Accelerator JCE Provider (**JIRA: PROD-8473**). *For more details, refer to the* [*Developer’s Guide: DSM Accelerator JCE Provider*](/v1/docs/dsm-accelerator-jce-provider-developer-guide)*.*
- **DSM Accelerator Webservice:**
  - Added local cache export support in DSM Accelerator Webservice (**JIRA: PROD-8473**). *For more details, refer to the* [*Developer's Guide: DSM Accelerator Web Service.*](/v1/docs/dsm-accelerator-webservice-developer-guide)

## 3. Known Issues

- When you edit the **starting time** of a Key rotation policy for a security object with the value as single digit time, for example: 01:00 am, it shows an error “**Invalid date/time selected. Please make sure you filled in a valid 12-hour time**”(**JIRA: ROFR-4786**). **Workaround:** Re-enter the rotate start time by removing the “0” before the single digit time and enter a new time (e.g. 01:00 am to 2:00 am).
- After downgrading Fortanix DSM to version 4.25, it still shows the **Node size** field with a null value for LMS keys that were added in DSM version 4.26, even though the Node size is not a supported parameter in the older version (**JIRA: PROD-8278**).
- Unable to create an LMS key with the following height combinations of 20.
  - 5, 20, and vice versa
- The hyperlink color for the field “Follow the instructions in” in the “Add Instance” form for Google Workspace Client-Side Encryption (CSE) still reflects the old link color value (**JIRA: ROFR-4789**).

![Screenshot from 2024-02-26 16-30-19.png](https://cdn.us.document360.io/c3bd85d2-4ad8-4d85-9f60-f1c168a3aad9/Images/Documentation/26219795087892)

**Figure 2: Client ID of CSE Application**
- The sync key API returns a “400 status code and response error” if its short-term access token expires during the synchronization of a group linked to AWS KMS (**JIRA: PROD-3903**). **Workaround**: increase the timeout of the temporary session token beyond the expected duration of the sync key operation.
- `exclude` does not work in the `proxy` configuration for operations such as attestation **(JIRA: PROD-3311)**.
- Rotating a GCP BYOK key to a pre-existing Fortanix DSM-hosted key (**Rotate to DSM key**) is not supported **(JIRA: PROD-6722)**. **Workaround:** You can manually copy an existing AES 256 key from a normal DSM group to a GCP-backed group. This key automatically becomes the currently active crypto key version in the GCP key ring.
- The “Rotate linked key” feature fails with an error for keys in an externally backed group where the external entity is a Google Cloud Platform key ring **(JIRA: PROD-6828)**. **Workaround:** You must first manually rotate the source key in the regular DSM group and then copy the rotated key to the GCP group.
- If an Azure key is rotated and then soft-deleted, only one version of the key is soft-deleted **(JIRA: PROD-6947)**. **Workaround**: Perform a key scan in DSM to synchronize the key state with Azure.
- The `create` operation for security object creation does not work for the Azure Managed HSM plugin **(JIRA: PROD-7078)**.
- The retry mechanism does not work as expected in the DSM Accelerator Webservice **(JIRA: PROD-7068)**.
- Copying an RSA or EC key from a normal DSM group to an AWS KMS-backed DSM group does not work as expected and results in an error **(JIRA: PROD-7787)**. **Workaround:** Export the RSA or EC key from the normal DSM group and import it into the AWS KMS-backed DSM group.