faspex 1.6 Release Notes

faspex 1.6 Release Notes
Version 1.6
July 20, 2009
What's New
  1. Integration with Enterprise Server 2.2.1 and Enterprise Server 2.5
  2. Improved security:
    • New configurable security options (deactivate after x failed logins attempts, prevent concurrent login, session timeout)
    • HTML escape user-entered fields
    • Homogenize error messages (to not divulge information about valid user accounts)
    • New Apache security items to enforce using SSL
  3. Specify minimum version for Aspera Connect, and warn users if they are using a lower version
  4. Active Directory Integration - Can import Active Directory users and groups into faspex, authenticating users and controlling their account status through Active Directory
  5. Multi-server implementation - Failed package relay notification email: if the Faspex server is unable to connect to the other Faspex server to relay a package over, an email notification will be sent to the sender
  6. Admin can send new password to user when editing user account
  7. Add build version number to UI
  8. Configurable package pathname prefix
  9. Package download stats for senders and admins
  10. Timestamps in faspex logs
  11. Announcement field available for admin to display message on login screen for all users
  12. Workgroup admin can now remove users he or she created
Fixed Issues 
  1. Post-processing bug fixes
  2. Sync all security settings in multi-server mode
  3. Show external email recipients in user's addressbook
  4. Symbols in package titles for as_faspex now work correctly
  5. Fixed memory leak issues on Windows
Known Issues 
  • Multi-server faspex:
    • After adding another faspex server, need to manually set the default server (in Home Server Rules) for correct slave server behavior
    • Currently only support 2 faspex servers
  • The Windows MSI does not support upgrades from 1.5.0.  Contact Customer Support for additional information how to upgrade from 1.5.0 to 1.6.0.
Have more questions? Submit a request

0 Comments

Article is closed for comments.
Powered by Zendesk