older versions of firefox for aspera connect

Workaround: Installing Faspex after upgrading the common components will recreate the missing link during the installation process. #31212 - (Linux Only) Upgrading the common components from older versions of 1.1 to any newer version deletes the /usr/bin/asctl symlink. #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. Workaround: Create the following path in your Windows Faspex server: #34716 - (Windows Only) Verifying SSL on node connections fail because the default certificate location is a hard-coded path that does not exist. Client Applications: There is only one SAML configuration and the one SAML configuration is specified as the default SAML configuration.Mobile Applications: There is a SAML configuration specified as the default SAML configuration with one or more SAML configurations.Workaround: Designate a default SAML IdP or upgrade to the iOS Faspex 3.0.0 mobile application.Īt this time Faspex with SAML authentication is supported for Aspera mobile and client applications in the following cases: 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. This issue is fixed in the iOS Faspex 3.0.0 mobile application. #35516 - In Drive 1.3.0 package uploads fail when sending to dropbox along with any other recipient.ĭate type metadata fields in the iOS Faspex 2.2.2 mobile application do not appear. #35569 - On iOS Faspex custom inbox packages that fail relay still appear in the inbox feed. #35681 - Date type metadata fields in the Android Faspex mobile application appear as regular text fields with no date selector shown. Note:Transfers to Faspex with an Azure default inbox is still supported in Drive 1.2.3.

Older versions of firefox for aspera connect