IBM Aspera Faspex 4.0.4 Release Notes

  • Product Release: April 28, 2017
  • Release Notes Updated: April 28, 2017

This release of IBM Aspera Faspex for Windows provides the new features, fixes, and other changes listed below. These release notes also list system requirements, including supported platforms, and known problems.

NEW FEATURES

  • Faspex now supports a rake task for configuring the HTTP fallback setting.
  • You can now use the Faspex health check url to check the status of Faspex nodes to provide information to load balancers. The url is
    https:/faspex_ip_address/aspera/faspex/health_check
    For more information, see IBM Aspera Faspex Admin Guide: Using the Health Check URL.

ISSUES FIXED IN THIS RELEASE

FASPX-251 - Users experience a long delay (10s) when logging in or logging out while Faspex queries the node's status.

SYSTEM REQUIREMENTS

IBM Aspera Enterprise/Connect Server: A licensed version of ES 3.6.0+.
IBM Aspera Connect Browser Plug-In 3.6.1-3.7.0

Windows
XP, 2003, 2008, 2012

Browsers:
Internet Explorer 9-11, Firefox 27-44, Safari 6-9, Google Chrome 40-48
(Faspex users can successfully access Faspex from any of these browsers on any OS, as long as the browser and OS are also supported by Connect)

Drag-and-Drop Support

Faspex supports the dragging and dropping of files and folders for transfer, but this support varies by platform and browser. See the table below for details on how this release of Faspex supports drag-and-drop in your environment:

Browser Windows Client Mac OS X Client Linux Client
Firefox Files and folders Files and folders Drag-and-drop not supported
Chrome Files and folders Files and folders Drag-and-drop not supported
IE 8 and 9 Files and folders
IE 10 and 11 Files
Edge Drag-and-drop not supported
Safari Files and folders

PACKAGE INFORMATION

Windows: AsperaFaspexSetup-4.0.4.142446-windows-32-msvc2012.exe
md5: fa46e6c4654af60795d9fa445e03136d
sha1: 8d8497df17b5ccc4719a9922a68771f99a54f5cb

KNOWN ISSUES WITH MOBILE AND CLIENT APPLICATIONS

#35934 - When an Azure cluster is used as the default inbox, transfers performed by Drive 1.3.0 and Outlook Plugin 1.3.3 fail. This issue will be fixed in subsequent releases of these client applications.
Note: Transfers to Faspex with an Azure default inbox is still supported in Drive 1.2.3.

#35681 - Date type metadata fields in the Android Faspex mobile application appear as regular text fields with no date selector shown.

#35569 - On iOS Faspex, custom inbox packages that fail relay still appear in the inbox feed.

#35516 - In Drive 1.3.0, package uploads fail when sending to dropbox along with any other recipient.

Date type metadata fields in the iOS Faspex 2.2.2 mobile application do not appear. This issue is fixed in the iOS Faspex 3.0.0 mobile application.

When configuring a SAML user against a multi-SAML server that has no designated default SAML IdP, the iOS Faspex 2.2.2 mobile application crashes. Workaround: Designate a default SAML IdP or upgrade to the iOS Faspex 3.0.0 mobile application.

At this time, Faspex with SAML authentication is supported for Aspera mobile and client applications in the following cases:

  • Mobile Applications: There is a SAML configuration specified as the default SAML configuration with one or more SAML configurations.
  • Client Applications: There is only one SAML configuration and the one SAML configuration is specified as the default SAML configuration.

KNOWN ISSUES WITH FASPEX V4 API'S

Important: Inclusion of Faspex V4 API's is experimental for this release and there may be issues when using it.

#35522 - Forwarding a package with the Faspex V4 API does not work.

#35093 - Content Encryption-at-Rest (EAR) cannot be requested through V4 APIs (EAR options are not functional). However, server side EAR (enabled on the destination node) should still work.

KNOWN ISSUES WITH 508 COMPLIANCE

FASPX-22 - On the Received and Send pages, when JAWS reads inactive links, it reads the associated page numbers but fails to read the word "disabled".

FASPX-21 - On the Send page, JAWS does not read the package name together with the archive or delete button name.

FASPX-20 - On the New Package page, in the Contacts dialog, JAWS does not read the full list of available users that can receive a package.

FASPX-18 - On the New Package page, JAWS reads "Cc:" twice for the Upload and Download check box

KNOWN ISSUES

#35983 - After changing inbox destination, downloading content of previously sent packages fails with an error.

#34716 - (Windows Only) Verifying SSL on node connections fail, because the default certificate location is a hard-coded path that does not exist. Workaround: Create the following path in your Windows Faspex server: C:/Users/Luis/Code/luislavena/knap-build/var/knapsack/software/x86-windows/openssl/1.0.0m/ssl/cert.pem

#33755 - When using symlinking with Enterprise Server 3.5.6, symlinked folders do not display in Faspex as folders, but the folder still download correctly.

#31212 - (Linux Only) Upgrading the common components from older versions of 1.1 to any newer version deletes the /usr/bin/asctl symlink. Workaround: Installing Faspex after upgrading the common components will recreate the missing link during the installation process.

#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 tlsv1.2.

#29547 - (Windows Only) Faspex displays an SSL error when adding a node with ssl_protocol set to tlsv1.1 or tlsv1.2.

#25002 - Bad display on IE 9 for overlay of Connect on the 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.

#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.

#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.

#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.

#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.

#16846 - If you are upgrading from Faspex 2.X and the transfer server is already set up on a different server, asctl does not handle this case. Please contact Aspera Support for assistance.

#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.

#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.

#16519 - (Linux Only) Some Faspex configuration settings (for example, 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 configurations 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.

#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.

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.

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.
Powered by Zendesk