Release Notes: IBM Aspera High-Speed Transfer Server, High-Speed Transfer Endpoint, and Desktop Client, 4.4.3

Product Released: September 26, 2023.
Release Notes Updated: September 26, 2023.

This release of IBM Aspera High-Speed Transfer Server (HSTS), High-Speed Transfer Endpoint (HSTE), and Desktop Client provides the new features, fixes, and other changes that are listed in the following sections. In particular, the Breaking Changes section provides important information about modifications to the product that might require you to adjust your workflow, configuration, or usage. Additional sections cover system requirements and known problems.

New features

Added support to Watchfolders for using multi-session mode for transfers in parallel. (Aspera #20)

Added a new configuration option 'db_cert_file' to specify the certificate that is used to enable and verify TLS connections to the configured Redis server. (Aspera #807)

Added support for specifying URIs as source and destinations in async. (Aspera #991)

Added support to async to use local Basic and Bearer tokens. (Aspera #992)

Added support for reporting HTTP fallback transfers activity through the Node API. (Aspera #1133)

SSH Pull watchfolder to work without a token. (Aspera #1191)

Added support for newer algorithms that allow the transfer tools to connect as clients to servers that require rsa-sha2-256 and rsa-sha2-512 signatures on public and private key authentication. (Aspera #1484)

Added support for specifying a replacement character in asperatrapd if object names contain XML control characters. (Aspera #1550)

Added additional settings to the pvcl_cloud library to control how it connects to Cloud Object Storage servers. (Aspera #1691)

Added support to async to use Node user bearer tokens for transfer authorization. (Aspera #1726)

Issues fixed in this release

Aspera #69 - Fixed an issue where transfers that are returned by /ops/transfers using iteration tokens might return inconsistent or duplicate results.

Aspera #838 - Fixed an issue where access keys might not be updated to modify the credentials if the previous credentials had expired.

Aspera #850 - Fixed an issue where configuration setting in aspera.conf associated with a Local Group in a domain environment would not be applied.

Aspera #887 - Reduced the default verbosity of the log messages generated by the pvcl_cloud library.

Aspera #1120 - Fixed a potential memory leak in ascp when running in persistent mode.

Aspera #1204 - Fixed an issue where the expiration of tokens that are issued by the Cloud Object Storage service might not be properly managed when using the pvcl_cloud library.

Aspera #1347 - Reduced the default verbosity of the log messages generated by the asperarund process.

Aspera #1354 - Fixed an issue where async jobs might be terminated if a file is removed from the source system while it is being processed for synchronization.

Aspera #1386 - Fixed an issue where async would repeatedly assign the same paths to transfer processes that had terminated with an error.

Aspera #1391 - Fixed a performance regression when downloading from Cloud Object Storage using asperatrapd.

Aspera #1423 - Updated and resolved the problem that prevented asperanginx from starting correctly in 4.4.2.

Aspera #1528 - Fixed an issue where it is not possible to register or use an entitlement license when deployed on Microsoft Windows in 4.4.2.

Aspera #1534 - Fixed an issue where asperarund sometimes does not stop asperawatchd or asperawatchfolderd processes.

Aspera #1544 - Fixed a resource leak in asperanoded when 'activity_logging' is enabled and there are no access keys.

Aspera #1547 - Fixed an issue where a PUT request to update an access key would be rejected if the payload contained an 'id' field with the same access key ID.

Aspera #1577 - Fixed an issue where transfers token generated through a request to the '/files/download_setup' API endpoint might not work when the payload request specifies a "source_root" path.

Aspera #1698 - Fixed an issue where transfers that use client-side encryption would result in an undecryptable file if the file_checksum_cache configuration setting is explicitly disabled in the server.

Aspera #1737 - Fixed an issue where asperanoded might not be able to correctly retrieve credentials for transfer processes set using Credential Manager on Microsoft Windows.

Aspera #1807 - Fixed an issue where a PULL hotfolder might stop processing new files and cause a crash in the asperasync.exe process when stopped.

Other changes

Aspera #445 - Changed how asperanoded handles transfers submitted through the /ops/transfers API endpoint to avoid having to clear the transfer queue manually at times.

Aspera #1549 - Improved upload performance that uses the pvcl_cloud library to write to Cloud Object Storage.

System requirements

Linux 64-bit: RHEL 7, 8, 9.  Ubuntu 20.04 LTS. Ubuntu 18.04 LTS. SUSE Linux Enterprise Server (SLES) 12. Debian 10+. Kernel 3.10 or higher and Glibc 2.17+. Rocky Linux 8, 9. Amazon Linux 2. Amazon Linux 2023.
Windows: Windows Server (64-bit) 2012, 2016, 2019, and 2022. For client use only, you might also use Windows 10, 11 (64-bit).
macOS: 10.15 (Catalina), macOS 11.0 and 11.1 (Big Sur).
PowerLinux: RHEL 7,8,9. CentOS 7. Ubuntu 20.04 LTS. Ubuntu 18.04 LTS. Your OS version must support little-endian (LE) ordering, and it must run on IBM Power hardware that supports LE ordering. Kernel: Linux 4.4.0-116-generic. Architecture: ppc64-le.
zLinux:  Linux on z Systems s390, 64-bit. RHEL 7,8,9. SUSE Linux Enterprise Server (SLES) 12.

Product support

For online support, go to the IBM Aspera Support site at https://www.ibm.com/mysupport/. To open a support case, log in with your IBMid or set up a new IBMid account.