Release Notes: IBM Aspera Console 3.3.1
Product Release: January 17, 2018
Release Notes Updated: January 18, 2018
This release of IBM Aspera Console 3.3.1 provides the new features, fixes and other changes listed below. These release notes also list system requirements, including supported platforms, and known problems.
- Console now supports transfers between two Node API endpoints.
- Console now supports transfers using Shares login credentials as endpoints.
- You can now choose to use ascp4 for transfers in the Console UI, as long as the endpoints support ascp4. For more information about ascp4 support, see http://asperasoft.com/company/support/auxiliary-transfer-features/.
- You can now specify a forward proxy when creating or configuring watch folders.
- Console now supports the following options in transfers between Node API endpoints when
the nodes are running Enterprise Server 3.8+:
- Preserve access timestamps: preserve_access_time
- Preserve creation timestamps: preserve_creation_time
- Preserve modification timestamps: preserve_modification_time
- Source Archiving: move_after_transfer
- Destination Deletion: delete_before_transfer
- You can now configure the system users and groups associated with Console and Aspera Common Components (MySQL and Apache) using environment variables.
- Console now supports the Job Timeout default configuration option. (CIM-944)
- Console now supports multiple SAML certificate fingerprint algorithms. (CIM-800)
- Console now supports a rake task to encrypt and decrypt the database.yml configuration file.
- Console now includes a rake task to add managed nodes. (CIM-1007)
- Due to licensing changes, Console no longer enforces max_user limits.
- [Linux] Console version of OpenSSL upgraded to 1.0.2.
AC-589 - From time to time, Node Poller reports "FaspNodeError::NodeApiUnreachableError" error for different threads. (CIM-1059)
AC-587 - Console has a cross-site scripting vulnerability using the jlist_status parameter. (CIM-1067)
AC-563 - Recurring Smart Transfers go immediately into the "Queued" status and never un-queue. (CIM-1021)
AC-554 - Console occasionally reports that a Sync session failed ("DB never reported a session end") even though the session is successful. (CIM-775)
AC-536 - Console Smart Transfers do not fail over when there are too many transfers in the queue. (CIM-942)
AC-534 - The error message is unclear when Console rejects a watch folder configuration because of an expired license.
AC-529 - It is possible to spoof content in Console due to URL appending in Apache. (CIM-908)
AC-527 - Sessions are incorrectly marked as inactive when monitoring multiple access keys on the same cluster.
AC-523 - Empty source_path value causes Console api /api/transfers/ID to report Unprocessable Entity error. (CIM-860)
AC-520 - Console now allows users to enter the fullpath of a SSH key instead of just the filename when uploading a SSH key to Console.
AC-514 - If a simple transfer or smart transfer with Console is initiated by a node running Linux on z Systems, the transfer fails.
AC-475 - You can now preserve customizatoins in my.cnf when upgrading Aspera Common Components by including !include /opt/aspera/common/mysql/my-custom.cnf at the end of the file. (CIM-578)
AC-474 - There is a broken link in the installation instructions. (CIM-582)
AC-456 - Console database.yml configuration file contains the password for the MySQL database in clear text.
Windows Server: Windows 2008 R2, 2012, 2016
Linux: Red Hat 6-7, CentOS 6-7, SUSE 11-12
Aspera Common Components 1.2.22
Browsers: Internet Explorer 8-11, Firefox 27-57, Safari 6-11, Chrome 40-63
IE Browser Compatibility mode is now supported.
md5: cbcdba24473739428315a9d2cd5fcdfb sha1: f45bd5fc711cb57530bad4691d117d051c7d6b3b
md5: 1356819592b521d6d7773f97fbbde71d sha1: 9fe14d1094a79dde0cd699ffc26cbcda24c5ef92
md5: 2cc945f92555b9d4df1d0fc347d74d14 sha1: 8f2582dfc9defdfc27aa70db7ceedae1abee64fd
AC-592 - Console Space Watcher service is unable to start when the service is not running but the pid file exists. (CIM-1060)
AC-561 - Console does not support the exclude files by timestamp (exclude_newer_than and exclude_older_than) options in transfers between Node API endpoints.
AC-549 - Console shows encrypted async transfers as not encrypted, due to issue found in Enterprise Server 3.7.3 and Enterprise Server 3.7.4
AC-583 - SSL error appears randomly when users browse nodes.
AC-494 - Console cannot display account information for Windows managed nodes if the username contains a space, returning the error "undefined method 'downcase' for nil:NilClass". (CIM-589)
AC-483 - When creating a Watchfolder on a local node that has only Node API credentials, adding a new folder fails with a timeout error.
AC-468 - When running a Report with Report on set to last week, the query is run for the correct time frame but the Report Period End displayed in the report title is incorrect. (CIM-498)
AC-442 - The "Node API" endpoint type is not supported for clusters or unmanaged nodes.
- Start MySQL.
$ /etc/init.d/aspera_mysqld start
- Log into the Console database as
$ /opt/aspera/common/mysql/bin/mysql -uUSERNAME -pPASSWORD aspera_console
- Edit the users table to allow long text
# ALTER TABLE users MODIFY view_filter TEXT;
- Stop MySQL.
$ /etc/init.d/aspera_mysqld stop
- Continue with your upgrade.
$ asctl console:upgrade
AC-398 - The Console dashboard returns a 500 Internal Server Error if a transfer session becomes stuck. (CIM-335)
AC-378 - When using failover groups, custom transfer settings do not propagate to the failover node. (CIM-296)
AC-376 - The Console map does not display in the Microsoft Edge browser. Microsoft Edge is not yet supported. (CIM-266)
AC-375 - When a transfer session fails to initiate, an incomplete record might be created that displays in Console but cannot be deleted. Workaround: Manually delete the session from central-store.db. (CIM-253)
AC-180 - If a managed node is removed from Console, attempting to delete saved endpoints associated with it from Preferences returns a 500 Internal Server Error.
AC-117 - After restarting Watchfolder services, the details page in Console does not display previously transferred files. This is issue will be fixed in an upcoming release of Enterprise Server.
NODE-137 - The Node API reports an incorrect count of failed files.
NODE-133 - The Node API reports the incorrect completion time for a transfer.
NODE-123 - If a transfer is canceled or it errors out, and it is retried before Console has a chance to poll the node, Console fails to mark the file as errored and instead adds a new file record when resuming the transfer. Both the original and new record appear in the Session Files table on the Session Details page, but the original record remains a normal, green bar and is never updated.
#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.
#27236 - Console generates reports of the type XLSX (rather than XLS). Any reports completed before upgrading from a version of Console prior to 2.5 are no longer accessible through the web link. However, any reports that were not completed before the upgrade (such as scheduled reports) are unaffected: a report configured to generate XLS generates XLSX when it next runs. Workaround: Click Rerun on a completed report.
#22396 - If upgrading from a version of Console prior to 2.0.1, 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 the upgraded.
#22303 - If upgrading from a version of Console prior to 2.0.1, 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.
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.