Release Notes: IBM Aspera Console 3.0.5
Product Release: February 10, 2016
Release Notes Updated: February 10, 2016
This release of IBM Aspera Console for Windows and Linux is a general maintenance release.
ISSUES FIXED IN THIS RELEASE
#34409 - The "submit simple transfer" API call cannot be executed through a FASP proxy.
#34405 - Filepaths are left blank in email notifications for hot folder transfers.
#34404 - Console web UI becomes unresponsive when running a long report.
#34337 - The Session Details page displays "Source" instead of "Destination" for the Initiator for external pull transfers.
#34336 - Email notification rule based on source IP addresses does not work.
#34232 - Pagination is broken on the Watch Folder page.
#33982 - Node v3 license pollers do not run when an entitlement_node_username exists in the localhost node's redis database.
#33729 - Simple / Smart transfers initiated in Console fail if the user does not have <schema_validation>disable</schema_validation> set in the source node's asperacentral configuration.
Windows: 2008r2, 2012
Linux 64-bit: RedHat 6-7, CentOS 6-7, SUSE 11
Aspera Common Components 1.2.15
Browsers: Firefox 27+, Safari 6+. Internet Explorer 8+. Chrome 40+
PREVIOUS RELEASE NOTES
md5: 8d0db38efb4d3c4dd481e000eb65bc43 sha1: 033baec4cf537f364d50ac6f675250fff0f84e5e
md5: 54bb85f0676ff89a54c37b9dbe5bc357 sha1: f487997a0eb7cc4e79bbf1e54000dde229f442fd
#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.
#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. 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.
#27236 - As of Console 2.5+, because Console now generates reports of the type XLSX (rather than XLS), any reports you completed before upgrading to this release of Console are no longer 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.
#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.
#22303 - Scheduled smart transfers that were created before upgrading from a version prior to 2.0.2 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.
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.