--- title: "[0.5.34] - Nov 19, 2024" slug: "0-5-34-nov-19-2024" updated: 2026-08-19T10:24:04Z published: 2026-08-19T10:24:04Z canonical: "support.fortanix.com/0-5-34-nov-19-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. # [0.5.34] - Nov 19, 2024 This article provides an overview of new features, improvements, and resolved issues in the Fortanix Data Security Manager (DSM) - Terraform 0.5.34 release. ## 1.0 New Features - Added support for assigning new or existing groups to an existing application (app) in Terraform Provider (**JIRA: PROD-9520**). *For more details, refer to* [*Clients: Terraform Provider*](/v1/docs/fortanix-dsm-clients-terraform-provider)*.* ## 2.0 Improvements - Modified the Terraform Provider processing mode from parallel to sequential to mitigate throttling exceptions while importing DSM AWS Security Objects key material. A locking mechanism has been implemented in `dsm_aws_sobject` to ensure that only one request is executed at a time (**JIRA: PROD-9443**). - Updated the **Fortanix** namespace description on the Terraform Provider GitHub homepage (**JIRA: PROD-9454**). ## 3.0 Bug Fixes - Fixed the following issues in the Terraform Provider AWS Sobject (**JIRA: PROD-9439**): - Fixed RSA and EC keys `key_ops` issue on the AWS Sobject documentation. - Fixed the issue where Terraform detects changes in `key_ops` after creating a `dsm_aws_sobject`, even when no changes have been made. - Fixed the error when creating a `dsm_aws_sobject` without an AWS key policy, then assigning the policy during an update. ## 4.0 Known Issues - `gcp_sobject` resource detects change even if nothing was changed in the Terraform Provider (**JIRA: PROD-9271**). - When you invite a user to a Fortanix DSM account as an account member and add this user to a group as an account administrator using the `dsm_group_user_role`, even though the user has not accepted the invitation to join the account, the user will still fail to be added to the group (**JIRA: PROD-9349**). - The following operations are not supported in the Terraform Provider admin app (**JIRA: PROD-9265**): - Disabling the admin app - Setting OAuth for the admin app - Setting allowed IP address for admin app - Creating an admin app with authentication methods such as WorkSpaceCSEAuth and JSON Web Token - Changing the authentication method expiry on the User Interface (UI) - SAN of type `Directory name` when creating admin app of type Trusted CA - Changing authentication method - Terraform detects changes to `deactivate_rotated_key` and updates its value from `false` to `null`, even though it is not explicitly specified in the key rotation policy (**JIRA: PROD-9529**). ## 5.0 Downloads The Fortanix Terraform provider can be accessed from the Fortanix downloads page - [https://fortanix.zendesk.com/hc/en-us/articles/6495657315348-Terraform-Provider](/v1/docs/dsm-clients-terraform-provider).