Deprecation notices

For more information related to Aspera on Cloud status and communications, visit the status page.

DSA public key for IBM Aspera ascp transfers

Effective January 31, 2025, the aspera_tokenauth_id_dsa public key will not be available for ascp transfers and will stop working with IBM Aspera managed transfer servers. After the deprecation date, any ascp transfers that rely on the aspera_tokenauth_id_dsa key will fail to authenticate. To avoid interruptions in your data transfer processes, you should migrate to RSA-based authentication for enhanced security and wider compatibility with current security practices. All versions of transfer clients currently supported will continue to work without any required changes. You may need to upgrade older clients as well as review and update custom integrations. For further assistance with this transition, contact our support team at https://www.ibm.com/mysupport/.

Sync feature in AWS environments with IBM Aspera Connect versions older than 4.1.3

On December 7, 2024, Aspera on Cloud will no longer support the Sync feature in AWS environments with IBM Aspera Connect versions older than 4.1.3. To continue using this feature, update Connect to at least version 4.1.3 or later. Alternatively, you can switch to the latest version of IBM Aspera for desktop to replace Connect. It is important to highlight that this will only affect the Sync feature in Aspera on Cloud in AWS, other features and cloud environments will not be impacted

Aspera on Cloud Activity App: Deprecation notice of file access page

On November 15, 2024, the File Access Page in the Activity App will be deprecated. The page will no longer be available, and any APIs associated with that specific feature will be disabled. This means that permission events from transfer nodes will not be collected for processing in the Activity app anymore. This will not affect file sharing nor setting permissions. Permissions settings for files or folders will continue to be retained.