IBM Aspera Shares 1.9.4 Release Notes
IBM Aspera Shares 1.9.4 Release Notes

IBM Aspera Shares 1.9.4 Release Notes

Product Release: September 16, 2016
Release Notes Updated: September 28, 2016

This release of IBM Aspera Shares 1.9.4 for Linux provides the new features, fixes, and other changes listed below.


  • Shares now displays the account status and expiration date (if applicable) of a user on the Users page (Admin > Accounts > Users).
  • The activity feed now includes items on Node API activity, including when the Node API creates and deletes files and folders.
  • Shares now supports a rake task to export a share's name and directory.
  • Shares now supports a rake task to configure a custom logo.
  • Removed the requirement that SAML users must have the given_name attribute to log in.
  • Shares now supports IPv6 by default. You can disable IPv6 by editing the nginx.conf file.
    Note: If IPv6 is disabled in Shares, you will need to either enable it in the system again or disable IPv6 ports in nginx.conf to have successful installation or upgrades. For more information see Disabling IPv6 Support in Shares at:

  • Shares now provides a Management REST API admins can use to manage Shares without the admin console in the web UI. For documentation on the API, see
  • Error logging for SAML response has been improved.
  • Updated Ruby on Rails to version
  • Updated OpenSSL to version 1.0.2h
  • Updated Nginx to 1.10.1.


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

  • Shares 1.9.4 requires version 3.6.1 of the Aspera Connect Browser Plug-In. You can install or upgrade to the latest version of the Connect Browser Plug-In when prompted by Shares or by downloading the installer from the website at
  • Shares 1.9.3 and later require a transfer server (Enterprise Server, Connect Server, Point to Point, or Aspera Client) version 3.6 or later to establish a connection to Shares. Trying to connect with an older version using the transfer server GUI fails with the error Could not generate DH keypair. Workaround: Aspera highly recommends upgrading to fix this issue as the latest product version maintain best security practices. Follow the instructions in this Knowledge Base article for a temporary workaround:


#34926 - Ruby SAML gem bug prevents users from authenticating via SAML with the error, "Invalid SAML response".

#34792 - Shares does not send new content notifications when connected to Aspera Transfer Cluster.

#33253 - The rake data:share:create command does not display error messages when failing.


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

Linux 64-bit: RHEL/CentOS 6 & 7

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


Linux 64-bit (rpm): aspera-shares-
md5: 27f148d470f340950a05c12cc733d178
sha1: cd1d0c520ce0e35fc8411feac3fd6683dec4d4ac


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

#35859 - Tags for transfers to Shares initiated by Aspera Drive do not have Share transfer ID(s).

#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 an older version of Aspera Drive (pre-1.2.0), 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.