IBM Aspera Faspex 3.9.2 Release Notes
- Product Release: July 1, 2015
- Release Notes Updated: July 1, 2015
This release of the IBM Aspera Faspex 3.9.2 for Windows and Linux includes bug fixes and support for IBM Aspera Connect Browser Plug-In 3.6.0.
ISSUES FIXED IN THIS RELEASE
#30749 - SAML assertion no longer fails for User Profile fields containing special characters.
#29894 - Uploads from Windows network share no longer fail when entering the network path manually using the Connect Browser Plug-In 3.5.2.
#13835 - Faspex cannot connect to an AWS mail server using TLS; however, SSL connects successfully. This is relevant to the settings under Server > Notifications > E-mail Configuration.
#16519 - (Linux Only) Some Faspex configuration settings (e.g. those that require system changes or asctl modifications) will not be restored when using the Faspex “Save/Restore” UI feature. For example, if the "Systemuser" flag is changed in faspex.yml, and the configs are backed up and restored to a new instance, the application will not start because the user must be created on the new instance with appropriate permissions. Another example is the "uri_namespace," which--if changed before a backup--must be updated in Apache using the “uri_namespace” command upon restoring. Other settings in faspex.yml include "HTTPPort", "HTTPSPort", etc, which will be overwritten to the previous values and may require manual steps toe ensure the ports can be used.
#16520 - If you download the Faspex db+config folder (from Server > Configuration > Save/Restore), the file will be saved to the browser's default location.
#16715 - If you set an alternate address (Server > Configuration > Web Server) on your source server and save your Faspex db+config folder (Server > Configuration > Save/Restore), then upon restore to a new server/instance, the alternate address will still be set on the new server. Subsequently, your email notifications will include an alternate address link to an instance which may not be up and running.
#16846 - If you are upgrading from Faspex 2.X and the transfer server is already set up on a different server, asctl will not handle this case. Please contact Aspera Support for assistance.
#17011 - Safari on Mac downloads the Faspex backup file to a tar file. Users can change their Safari preferences so that archive files aren't automatically unzipped.
#17089 - After restoring Faspex 3.X from a source server, the destination server may or may not be able to verify the SSL certificates presented by a node (depends on whether the source server had a valid cert file or if it was missing altogether). Administrators should check to see if the cert.pem file exists and back it up prior to restoring.
#17652 - For an existing Faspex DS group: If this group is moved to another Organizational Unit (OU) on the DS server, and then the group is synced on Faspex, the group will become invalid on Faspex.
#21984 - On Centos 6.0 & 6.2, after installation and asctl faspex:setup has run and completed, users may see an invalid license message appear on the login page, even if they have copied over the correct aspera-license file to their /opt/aspera/etc directory.
#25002 - Bad display on IE 9 for overlay of Connect plugin of Faspex new package page. Workaround: This is an IE issue, you should upgrade to the latest browser version supported on your platform or ensure that you have the latest IE updates applied.
#27371 - ADFS SAML users running Chrome 36.0 on a Windows machine are currently unable to login. Workaround: Use a different browser to login as an ADFS SAML user.
#29547 - (Windows Only) Faspex displays an SSL error when adding a node with ssl_protocol set to tlsv1.1 or tlsv1.2.
#29531 - (Linux Only) Stats-collector displays an error when working with nodes that are configured for tlsv1.1. The Linux version of Faspex only works with SSLv3 or tlsv1.2.
- IBM Aspera Enterprise/Connect Server: A licensed version of 3.3+.
- RedHat 6-7, CentOS 6-7, SLES 11
- XP, 2003, 2008
- Browsers: Internet Explorer 8+, Firefox 27+, Safari 6+, Google Chrome 32+
PREVIOUS RELEASE NOTES
- Linux (rpm): aspera-faspex-22.214.171.124136-0.x86_64.rpm
- md5: ff0c9c83db83a93a24af476d91f15501
- sha1: 43f5dd89b8e0c46db553306db40383174bdc9026
- Windows: AsperaFaspexSetup-126.96.36.199695-windows-32-msvc2012.exe
- md5: e7c7220680431377b3806bb01e081b4e
- sha1: e322e1ea8690e4d8bd84975e56217f7b8cf1ca51
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.