Minor Release: IBM Aspera Enterprise Server/Connect Server/Point-to-Point/Desktop Client 3.7.2 for OSX

Product Release: January 17, 2017
Release Notes Updated: January 18, 2017

We are very excited to announce the general release of version 3.7.2 of IBM Aspera Enterprise Server (ES), Connect Server (CS), Point-to-Point Client (P2P), and Desktop Client (DC) for OSX. This latest OSX release since 3.6.2 extends the capabilities of Aspera's popular transfer server software to include a broad range of enhancements in response to Aspera’s user community feedback. This release includes a number of new features along with some fixes and other changes, as you will see below.

New enhancements are primarily focused around ascp, ascp4, Node API and the Aspera Watchfolder and Aspera Watch Service. Key features are categorized and detailed below. Please note we have highlighted some important modification information in the Breaking Changes section that may require you to adjust your workflow, configuration, or usage.

General What’s New Features

  • Added support for MacOS 10.12
  • Connections can now be created with an ATS subscription in the GUI
  • FASP transfers are more secure with upgraded OpenSSL to 1.0.2j
  • Special file permissions are now supported in ascp and the Node API when the permissions are configured in aspera.conf
  • A new option for Hot Folders in pull mode to download only the contents of a directory and not the directory itself.
  • A man page is now available for asconfigurator in the admin guides
  • Support for Azure storage Block Blobs with maximum file sizes up to 4.77 TB and maximum block sizes of 100 MB
  • Hadoop Distributed File System (HDFS) and IBM Cloud Object Storage (Cleversafe) are now supported

Ascp Updates

  • Users can test a transfer without reading from disk and/or writing to disk by using a new transfer scheme, eliminating the need to generate large test sets
  • Users can now specify multiple SSH private keys in the same ascp command
  • SSH private key strings can now be used to authenticate ascp transfers
  • Two new ascp options extend support for base64 encoding to indicate that the destination path and the specified source prefix is base64 encoded
  • Enhanced performance, unencrypted CPU-bound transfers may see an increase of up to 100% in overall throughput; and encrypted CPU-bound transfers may see an increase in overall throughput of up to 20%
  • New FASP Manager API can be used to send an event with individual arguments

Ascp4 (A4) Updates

  • Log size can now be configured so that big transfers of many files (millions) are not overwritten before the session completes
  • ascp4 can now transfer to destinations with a UNC path set for the docroot
  • The path of a docroot in cloud storage is not required for ascp4 transfers
  • Exclude patterns are now supported, including those with cloud storage
  • A4 documentation is now included in the ES, CS, P2P, and DC guides
  • New options --delete-before and --delete-after are available in beta version

Node API Updates

  • A new Node API call returns usage data (bytes in, out, & total) by usage id
  • Node API now returns events for the creation, rename, and deletion of files using the Node API, in addition to file transfer events
  • A new Node API call returns verbatim the content of a file within the file size restriction set in aspera.conf
  • The access key and token secret of a Node API user are now passed on to Aspera Central, such that ascp is run with the environment variables associated with that user
  • SSH private key strings are now are now supported in the Node API
  • A new case-insensitive filter can return filename matches regardless of case to Aspera Files
  • Transfer API improved with new support for setting transfer rates, bandwidth priorities, and pausing/resuming/canceling active transfers
  • Improvements in support for content protection settings
  • Toekn authortization now uses SHA-2 by default over SHA-1
  • The status of files and transfers can now be reported by iteration token from the Node API
  • File modification events, including delete and rename, are now logged to redis/scalekv
  • Transfer and bandwidth statistics are self-cleaning for large numbers of sessions
  • Default and allowed SSL ciphers have been updated to eliminate support for 3DES and to align the defaults with hardened versions
  • Asperacentral has a new raw options capability that allows users to authorize the use of raw format ascp options

Watchfolder & Watch Service Updates

  • Users can now authorize the use of raw format ascp options by Watchfolder transfers
  • Watchfolders can now use token authentication for transfers
  • The Aspera Watch Service is now automatically enabled
  • Watchfolder transfers now work with Akamai storage
  • Support for force-send-after configuration for growing files, retrying failed drops, encryption at rest, and token authorization
  • New APIs for starting, stopping, and managing watchfolders across various user accounts and their access control
  • Many other enhancements to features and robustness

Sync Updates

  • Introduction of access key authentication providing an alternative to the security credentials of a user
  • A new asyncadmin option displays file attribute
  • Pending file bytes are now reported correctly in Aspera Console during an async pull
  • New recursive mtime option enables the exclusion of directories and files older than a configured timestamp
  • New option to delete operations in a unidirectional sync to be delayed until the end of the synchronization
  • Sync now preserves POSIX attributes in the event that file attributes change but file contents do not
  • Two new options for preserving timestamps

Breaking Changes

If you are upgrading from a previous release, the following changes for this release may require you to adjust your workflow, configuration, or usage.

  • With the implementation of new inline validation options, existing users with inline validation enabled must set the validation provider to uri or lua_script. The external option has been replaced by uri and the lua option has been replaced by lua_script
  • When upgrading to 3.7.2, if asperawatchd or asperawatchfolderd services are being run by users other than root, the services must be stopped prior to upgrade and restarted manually following the upgrade. Services run by root are migrated automatically during installation
  • Node API transfer account must have access control set to admin in order to create watchfolders
  • The way asperawatchfolderd uses docroots has changed
  • Recursive counts are now disabled by default, but must be enabled in order for Aspera Files to use this feature
  • Multi-session (parallel) transfers from 3.5 clients are no longer compatible with 3.6 and newer servers
  • New asynchronous “in transfer” post-processing engine with Lua scripts

How to Upgrade

This 3.7.2 release is available for download for each individual product listed below.  Aspera’s support team stands by ready to help you as needed with upgrades. If you have any questions or would like upgrade assistance, please contact support@asperasoft.com.  You can also read the full release notes which includes links the admin guides for each product and operating system.

  • Aspera Enterprise Server 3.7.2 is available for download here
  • Aspera Connect Server 3.7.2 is available for download here
  • Aspera Point-to-Point Client 3.7.2 is available for download here
  • Aspera Desktop Client 3.7.2 is available for download here

These releases are also available at the IBM Passport Advantage site.

Powered by Zendesk