Release Notes: IBM Aspera Shares 1.9.6 for Linux

Product Release: September 27, 2016

Release Notes Updated: September 27, 2016

This release of IBM Aspera Shares for Linux provides the new features, fixes, and other changes listed below. In particular, the Breaking Changes section provides important information about modifications to the product that may require you to adjust your workflow, configuration, or usage. These release notes also list system requirements, including supported platforms, and known problems.

NEW FEATURES

  • Shares UI
    • Shares now supports the new Manager Permissions configuration options that allow admins to determine whether managers can administer users and groups through the UI, the API, or both. Admins can configure these permissions using the Shares UI or the data:manager_config rake task.
    • Admins can now import a specific SAML user to Shares.
    • After users click the Delete button to confirm the deletion of a folder or file, Shares presents them the "Processing..." animation until the file or folder is deleted.
    • Error messages displayed in Shares when testing the configuration of a node in shares are more detailed and specific.
  • Rake Tasks
    • Shares now supports new rake tasks to delete LDAP users and groups.
    • Shares now supports a new rake task to add LDAP users to local groups.
    • Shares now supports a new rake task to configure a custom logo.
    • Shares now supports a new rake task to configure whether managers can administer users and groups through the UI, the API or both. Admins can configure these permissions using the Shares UI or the data:manager_config rake task.
  • Shares API
    • API users can now delete share permissions for users and groups.
    • API users can now update properties of a share.
    • API users can now update properties of a local group.
    • API users can now update a SAML user.
    • API users can now delete LDAP users and groups.
    • API users can now add LDAP users to local groups.
    • User management APIs previously only available to admins are now also available to managers of shares.
  • System
    • Shares no longer sends transfer notifications when files with zero bytes are uploaded to a share or when files are skipped in transfers initiated by IBM Aspera Console.
    • Shares now generates unique versions of the following files on a clean install:
      • dhparam.pem
      • cert.key
      • cert.pem
      • secret.rb
      • secret_token.rb
    • OpenSSl has been updated to version 1.0.2j.
    • Ruby has been upgraded to version 2.2.5.
    • Nginx SSL ciphers list has been updated to address the Sweet32/3DES vulnerability.

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.

  • By default, the Nginx web server in Shares is configured to listen on IPv6 ports in addition to the standard IPv4 ports. If your operating system does not support IPv6, Nginx is unable to start and Shares fails to load for your users. Disable Nginx from listening on IPv6 ports by following the instructions in IBM Shares Admin Guide:Disabling IPv6 Support in Shares.

ISSUES FIXED IN THIS RELEASE

#36251 - Share created using an API command is not immediately available for interaction.

#36089 - Bookmark icon stays red for a long time after the node comes back online and the bookmark is functional again.

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

#35784 - ATP clusters added to Shares show an error status even when at least one node is active.

SYSTEM REQUIREMENTS

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

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+, Safari 6-9, Google Chrome 32-48

PACKAGE INFORMATION

Linux 64-bit (rpm): aspera-shares-1.9.6.132631-1.x86_64.rpm
md5: 581790e8ddce5b0a31a8336ab5fe75dc
sha1: 96a492cf40b3f9f1493600db84d51d7ba23b0b10

KNOWN ISSUES

#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 127.0.0.1 and one with host localhost, the node with host 127.0.0.1 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.

PRODUCT SUPPORT

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.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk