IBM Aspera Console 3.0.2 Release Notes
IBM Aspera Console 3.0.2 Release Notes

IBM Aspera Console 3.0.2 Release Notes

Product Release: September 15, 2015
Release Notes Updated: September 15, 2015


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

New Features

  • Transfers: Console now allows configuration per node of the file suffix for partially downloaded files. The current default suffix is .aspx, but this can be changed by going to Nodes, editing the desired node, and going to Configuration > Advanced File Handling.
  • Graph: If enabled, Console tracks the total bandwidth usage across all nodes on the Dashboard graph. Enable by going to Configuration > Defaults.
  • Security: Aspera common components (including OpenSSL and Apache) are now updated to increase security and protect against the logjam threat.
  • Watchfolder: Watchfolder is an experimental feature in Console 3.0.2 and requires IBM Aspera Enterprise Server 3.6+. An updated Console with full Watchfolder support will be released at the time that Watchfolder is released as a fully supported feature.

Other Changes

  • Administrators: The Edit Permissions link no longer displays for admin users, and Console no longer redirects to the permissions page when creating new admin users.


#32145 - Users run into an error when deleting personal logins.

#32072 - Console does not throw an error when failing to select a specific weekday while editing a scheduled, weekly-recurring smart transfer.

#32066 - Editing an existing scheduled smart transfer does not allow you to change the existing schedule.

#32020 - When editing a directory service user, the Reports Allowed option is grayed out.

#31925 - You cannot create a new failover group when accessing Console from an IE 8 browser.

#31519 - Users with the Create Smart Transfers permission cannot edit created transfers.


Windows:  2008r2, 2012

Linux 64-bit:  RedHat 6-7, CentOS 6-7
Aspera Common Components 1.2.14

Browsers:  Firefox 27+, Safari 6+. Internet Explorer 8+. Chrome 32+


Linux 64-bit (rpm): aspera-console-
md5: fad9d2e220ddf1fdc2a855ddd92a0407
sha1: 2f180b639ba71d0be9c491b98b6ed63d77f057e5
Windows: AsperaConsole-
md5: 1373c2de8e85f528bf67c4cb2ee1ff2f
sha1: 66f06892896f1a3a57416d182a19e005632f502f
Aspera Common Components: aspera-common-
md5: 5dfac6c84865959494afd5df4836a945
sha1: 40cbd5b392e9f98b73d97e1adb5e83ca0a102833


#22303 - Scheduled smart transfers that were created before upgrading continue to use the old behavior, displaying dates/times using the timezone of the transfer requester, rather than trying to look up the recipient's time zone.

#22396 - If email notifications are configured for specific transfer paths on a user’s Preferences > Email Notifications page, these settings are not honored when the user clicks the Rerun link on the Activity page on a transfer that started before Console was upgraded.

#27236 - Because Console now generates reports of the type XLSX (rather than XLS), any reports you completed before upgrading to this release of Console will no longer be accessible through the web link. However, any reports that were not completed before the upgrade (such as scheduled reports) are unaffected: if a report was configured to generate XLS, when it next runs it will generate XLSX. Workaround: Click Rerun on a completed report.

#27371 - ADFS SAML users running Chrome 36.0 on a Windows machine are currently unable to log in. Workaround: Turn off "Extended Protection" in ADFS SAML IdP. After doing so, you may at first see ADFS SAML user login failures with an "Invalid SAML response" error and infinite redirects on login. After some time, however, the failures end.

#31098 - (Linux Only) Upgrading the common components from version 1.2.9 to any newer version deletes the /usr/bin/asctl symlink. Workaround: Installing Console or Orchestrator after upgrading the common components will recreate the missing link during the installation process.


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.