Release Notes: IBM Aspera Shares 1.9.7
Release Notes: IBM Aspera Shares 1.9.7

Release Notes: IBM Aspera Shares 1.9.7

Product Release:
Release Notes Updated: May 2, 2017

This release of IBM Aspera Shares provides the new features and other changes listed below. These release notes also list system requirements, including supported platforms, and known problems.


  • Updated Java version to JRE8u121.


IBM Aspera Enterprise Server licensed with Connect Server 3.6.0+.
IBM Aspera Connect Browser Plug-In 3.6.1-3.7.2

Windows 64-bit: 2008 R2, 2012 R2

Linux 64-bit: RHEL/CentOS 6 & 7

Note: Shares can also be installed on a machine running SLES 11, but this operating system is not officially supported by Aspera.

Browsers: Internet Explorer 8-11, Firefox 27-51, Safari 6-9, Google Chrome 32-56


Linux 64-bit (rpm): aspera-shares-
md5: dcd9746c74e7105670577801f1444745
sha1: d2c1e1cdf059db14958d8cd7540dc69b371bb077
Windows: AsperaShares-
md5: d3325271f1722544a711f3667937ed84
sha1: 9936aeb275bb90c0082b58c9b74b804c9b1e14f8


#36123 - SCP GUI transfers to and from Shares have float values instead of integer values for 'user_id' and 'share_id' in tags.

#29575 - If a share's name has a forward slash ("/") in it, this share cannot sync with Aspera Drive. The sync action fails, with a "Path not found" error. Transfers between these shares using the API also fail with a "Path not found" error.

#28359 - SSLv3 is disabled by default to address a security threat. If you are using a pre-1.2.0 version of Aspera Drive, upgrade Drive to the latest version.

#28143 - The Disabled checkbox (Admin > Directories > SAML > Security) for a SAML directory is not functional.

#27371 - ADFS SAML users running Chrome on a Windows machine are currently unable to log in. Workaround: Turn off "Extended Protection" in ADFS SAML IdP. Doing so at first produces random ADFS SAML user login failures with an "Invalid SAML response" error and infinite redirects upon login; but in the longer term, this does fix the problem.

#27228 - If the node is set to use EAR, downloading multiple encrypted files/folders or a single folder with encrypted files does not prompt for a password.

#27218 - If Shares is set to use EAR, HTTP fallback download of unencrypted content fails with numerous errors. Common errors include: "Insufficient permissions", "Server refused request", and "Connection Lost" errors.

#27188 - If Shares is set to use EAR, downloading a file that was not encrypted will ask for a passphrase.

#27187 - If the node is set to use Encryption-at-Rest (EAR) but Shares is not set to use EAR, downloading content that is a mix of encrypted files, unencrypted files, and files encrypted with a different password does not prompt the user for a password.

#26342 - When a local node is added to shares twice, one with host and one with host localhost, the node with host displays a stats collector error.

#25139 - For Shares servers that are installed on Windows, performing a share-to-share drag-and-drop transfer from a share that does not support share-to-share will trigger an "Internal error".

#25041 - Due to changes made by Google to its mail server’s handling of images in email (Dec 2013), the Aspera Shares logo is not displayed in email notifications. Customers not using a gmail server do not encounter this problem.

#18579 - If you perform a search for remote groups that start with backslash (\) or asterisk (*), Shares cannot find them.

#15396 - The transfer fails when you attempt to download special files like symlinks, block and character device files, socket, and so on.

#14532 - The transfer rate and encryption settings in Shares can be circumvented by users if they manually change the FASP URL before submitting. Workaround: In order to enforce the settings, set the desired values in the aspera.conf file on the node.

#12883 - When searching (browsing) recursively, the sort parameter is ignored.


For on-line support resources for Aspera products, including raising new support tickets, please visit the Aspera Support Portal. Note that you may have an existing account if you contacted the Aspera support team in the past. Before creating a new account, first try setting a password for the email that you use to interact with us. You may also call one of our regional support centers.