Release Notes: IBM Aspera Drive 1.3.0
Release Notes: IBM Aspera Drive 1.3.0

Release Notes: IBM Aspera Drive 1.3.0

Product Release: March 28, 2016
Release Notes Updated: March 28, 2016

WHAT'S NEW

Welcome to this release of IBM Aspera Drive. Drive 1.3.0 adds support for single sign-on (SSO), and includes several maintenance updates and improvements.

SYSTEM REQUIREMENTS

Windows

On your Aspera Drive client:

  • Windows 7, 8, or 10

On your transfer server, one of the following:

  • Aspera Shares 1.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Faspex 3.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
Note: If you require the synchronization feature, you must have Aspera Enterprise Server 3.5.x or higher with a Sync-enabled license.

Mac

On your Aspera Drive client:

  • OS X 10.8, 10.9, 10.10, or 10.11.

On your transfer server, one of the following:

  • Aspera Shares 1.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Faspex 3.8.1 or higher, with Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
  • Aspera Enterprise/Connect Server 3.5.x or higher with a Drive-enabled license
Note: If you require the synchronization feature, you must have Aspera Enterprise Server 3.5.x or later with a Sync-enabled license.

PACKAGE INFORMATION

Mac OS X: AsperaDrive-1.3.0.122512.dmg
md5: ef3e63b290d152c0812cf14325213758
sha1: 9c5d846dc6a680839840c14618084819088d32a2
Windows: AsperaDrive-1.3.0.122512.msi
md5: 6966adc3d2826dfd2b5ddb5337551d26
sha1: a79aed5187d20c03b97613ec67ee44d4861a3fa9

KNOWN ISSUES

  • #34965 - When you change the permissions for a SAML user in Shares, those new permissions settings are not reflected in Drive. To have the new permissions settings take effect, you must re-authenticate the user by re-adding that account to Drive.
  • #34952 and #34957 - [Windows only] With the PingFederate SSO provider, when you are logging into Drive, enter your login credentials and then press the Enter keyboard key (rather than using the Sign In button).
  • #34847 - If your transfer server's disk space is full, Drive may not offer the correct reason for the failed sync operations.
  • #34826 - [Mac OS X only] If you add a SAML account that uses an invalid certificate, Drive erroneously does not issue a warning.
  • #34722 - If a SAML account becomes invalid, Drive does not provide a way to re-enter the account credentials. To work around this issue, you must remove the account and then add it again.
  • #34585 - [Windows only] In Windows Explorer, when you browse in Drive and expand the tree hierarchy in the lefthand navigation pane, it does not correctly display directory contents.
  • #33590 - When you add a new account to Drive, Drive correctly warns you if it encounters an invalid security certificate. However, if users decline to trust the certificate, Drive erroneously proceeds, and users must decline it a second time.
  • #33457 - When you attempt to create a Drive account for a SAML user whose account in Faspex or Shares has been disabled, Drive does not issue an error or notification.
  • #33660 - Drive incorrectly offers options for SAML authentication, even if SAML has not been configured for your Shares transfer server.
  • #33384 - [Windows only] On Windows 10, Drive's shortcuts do not appear in the Quick access list in Windows Explorer.
  • #31919 - [Windows only] On Windows 8, if Drive accounts are created by the built-in Administrator user, the Aspera Drive option does not appear when you right-click files or folders in Windows Explorer. Workaround: When installing Drive, either install as a different user, or do a system-wide installation for all users.
  • #31869 - Node-to-node transfers are not supported. If you attempt a transfer from one node to another, the transfer fails and an error is recorded in the Drive Activity window.
  • #28181 - [Mac OS X only] Some configurations experience issues in syncing files with S3 storage.
  • #27587 - Temporary files that applications (such as Microsoft Office) create are excluded from sync transactions because they can cause conflicts. The affected files are those with names of the form ~$* or ~*.tmp.
  • #27277 - [Mac OS X only] This issue affects users who attempt to upgrade Drive versions lower than 1.2.0 using the "Check for updates" feature. When the user first attempts an automatic update, the update action fails with an error message:
    Failed to run update. Mount location not found:
    /tmp/AsperaDrive
    If the user attempts the automatic update a second time, the update succeeds.
  • #27153 - If the host is unreachable while Aspera Drive is sending a Faspex package, Drive may become unresponsive for approximately one minute.
  • #26725 - [Mac OS X only] An initial sync of a large number of files results in high CPU usage.
  • #26641 - Drive may encounter problems when it attempts to transfer files that have the same name but different case (for example, aspera1 and Aspera1).
  • #25913 - During a sync scheduled in Aspera Drive, even if files on the Shares server are changing (that is, are in the process of being downloaded), Aspera Drive nevertheless attempts to sync those files, resulting in file errors and conflicts.
  • #24193 - [Mac OS X only] When you right-click a file for the first time after Drive has been installed, the Send to Faspex option is not available. However, it is available on subsequent attempts.
  • #23230 - Aspera Drive cannot send packages to some valid Faspex usernames if those usernames contain the following special characters:

    < > ; ( ) &

  • #22789 - When a directory is renamed, then renamed again to its original name, the correct name may not appear in all Explorer windows.
  • #20513 - When you use Drive with Faspex to send a package to a dropbox, the dropbox name will not appear in the autocomplete options. Instead, you must type the dropbox name manually.

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.