faspex 2.5.1 Release Notes

faspex 2.5.1 Release Notes
Version 2.5.1
Platforms: Windows, Linux 32-bit and 64-bit (Centos, RHEL)
Created: 11/5/2011
What’s New
  • Built-in ad-hoc dropboxes for private, project-based submission of content from third parties, along with configurable metadata input, encryption-at-rest, and reporting through Aspera Console.
  • Support for multiple, customizable metadata profiles that can be assigned to individual dropboxes or normal package submissions.
  • Ability to configure instructions for the “New Package” send page
  • Email notification to sender for confirmation of upload result
  • Email notifications can now be configured to include link expiration information
  • Option on a per-dropbox basis to automatically save metadata to a text file within the package
  • Supports allowing users to choose encryption-at-rest on a package-by-package basis
  • Directory service integration; Faspex now supports Apple Open Directory and 389/Red Hat/Fedora Directory Server out-of-the-box and extensibility for additional directory services.
  • Management of workgroup and dropbox memberships from a Faspex slave server.
  • Transfer server cluster support, which includes load balancing to support more concurrent transfers and greater total bandwidth.
  • As of 2.5.0, databases merged so Faspex uses a single database (‘faspex’) instead of three (i.e., “central,” “faspex” and “user_service”)
  • Native 64-bit browser support on all platforms with Connect 2.7.3, added support for Chrome on Mac
  • “Forgot Password” feature now accepts email addresses in addition to username.
  • Support for Microsoft Outlook plugin, allowing Outlook users to email giant files transparently through Faspex
  • Default multi-server sync interval changed from 1 hour to 10 minutes
  • Workgroup admins can now always see and send to members, even when “Workgroup members sending to each other” option is set to the “restricted” level
  • Updated command line client to automate Faspex package uploads and downloads
  • Automation API now supports retrieving metadata when downloading packages
  • Includes third-party security audited enhancements


Fixed Issues
  • More robust communication between Faspex web app and transfer servers, including ability to catch up on transfer events that happened during network interruptions and maintenance windows.
  • Post-processing scripts now run on all package forwarding events, and scripts now have a ‘faspex_pkg_is_forward’ environment variable available (#11883)
  • Active Directory users with explicitly overridden home servers no longer lose home server settings during sync with directory service controller (#12095)
  • Active Directory (and LDAP) groups now remember and apply their initial settings to new users added to the group (#11227)
  • Checking all files in a package and downloading them now counted as a full package download (link expiration and package deletion policies get applied) (#8671)
  • Old Apache log files now automatically deleted by log rotation mechanism (#5355)
  • Corrected several edge cases that caused multi-server sync errors (#9726, #9884)
  • ‘Last login time’ field no longer overridden with older values during multi-server sync (#10317)
  • User auto-complete dropdown lists now show additional fields for each match, if available (first and last name, login, and email address) (#10416, #11761)


Known Issues
  • Directory service users must have non-null first name, last name and email addresses. (#12131)
  • Users upgrading from an older version of Faspex to Faspex 2.5.1 should install Faspex 2.5.1 without uninstalling the older version of Faspex; if the older version has been uninstalled, then the user should run “asctl mysql:set_root_password” before running “asctl faspex:upgrade” after installing the Faspex 2.5.1 package. (#11900)
  • During an upgrade on Windows XP 64-bit, if you encounter the following error during the “Installing Connect key...” step then follow the workaround.

Error: Error setting permissions on faspex user directory (1280) (RuntimeError)


Workaround:
Run the upgrade using the built-in Administrator account. (#10026)

  • During an upgrade on Windows 2008 32-bit when Apache attempts to restart, if you encounter the following error then follow the workaround.

Error: Apache HTTPD Server (Aspera): The application has failed to start because its side-by-side configuration is incorrect. Please see the application event log for more detail.


Workaround:
Install the Microsoft Visual C++ 2008 SP1 Redistributable Package (x86) package. The download link is at http://www.microsoft.com/downloads/en/details.aspx?FamilyID=A5C84275-3B97-4AB7-A40D-3802B2AF5FC2 (#11027)



Package Information
sha1sums:
  • 205ad7910bcaa7f56023601fc1296b053d61baaa aspera-faspex-2.5.1.45263-0.i386.rpm
  • 85645397bca4113e424b6fcec65007f7c73ec2c9 aspera-faspex-2.5.1.45263-0.x86_64.rpm
  • aa829889eea6f98d8b53651256e689cd794f82db AsperaFaspex-2.5.1.45263-windows-32.msi
  • 5c1b382bf4d699ca0ae7aeedf75064d068c7ffe0 aspera-common-1.1.4.44941-0.i386.rpm
  • e8feeb551cb4a7d331063c4a28902047b795c53c aspera-common-1.1.4.44941-0.x86_64.rpm

md5sums:
  • eeda4550dcb147827fe5d57dceb6a11a aspera-faspex-2.5.1.45263-0.i386.rpm
  • 13adffbb2decb96d9725936dbfc1047a aspera-faspex-2.5.1.45263-0.x86_64.rpm
  • 26f5d3f51d3ceb3645a3ffae8165e1eb AsperaFaspex-2.5.1.45263-windows-32.msi
  • ad96f694651c6e940b10de2fb6ff4f18 aspera-common-1.1.4.44941-0.i386.rpm
  • 085a5d2c733ebbfdeb74e1c6fdac6472 aspera-common-1.1.4.44941-0.x86_64.rpm
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk