Road map of IBM Aspera Faspex
IBM ASPERA FASPEX 4.4.1
Use Faspex and IBM Aspera High-Speed Transfer Server together to encrypt files before they are transferred, encrypt files at the destination, and encrypt data transferred over the network.
Relays:
Relays transfer copies of uploaded files to specified destinations (custom inboxes). There are two types of relays: package relays and file relays.
IBM ASPERA FASPEX 4.4.0.4
HTTP Gateway-based transfers are limited by the same limitations of HTTP/HTTPS transfers and the native download manager of the client’s web browser.
Download Limitations:
Since uploads and downloads leverage HTTP/HTTPS between the web browser and HTTP Gateway, the transfer performance depends on the performance of HTTP/HTTPS, which can be affected by distance between clients and servers, and by other network-related issues. For this reason, IBM Aspera highly recommends following best practice by deploying HTTP Gateway as close as possible to end users.
Empty (0-byte) files are not supported for uploads and download.
HTTP Gateway does not support resuming transfers.
IBM ASPERA FASPEX 4.4.0.3
Faspex and connect
Transfers initiated in the IBM Aspera Faspex web application are conducted using the IBM Aspera Connect Browser Plug-in. The Connect Plug-In is an install-on-demand web browser plug-in that facilitates high-speed uploads and downloads with an Aspera transfer server.
The connect install dialog
When a user first logs in, Faspex checks if Connect has been installed on their browser. If they have an outdated version or do not have the plug-in installed, Faspex prompts the users to download and install the plug-in.
IBM ASPERA FASPEX 4.4.0.2
Package Recipient Expansion by Email Address
Faspex automatically converts email addresses in recipient fields to existing Faspex users associated with the same email addresses. If there are multiple users associated with an email address, the address expands to all matching users. If a user exists whose username is the entered email address, the email address is not expanded and the package or notification is sent to that user only.
IBM ASPERA FASPEX 4.4.0.1
Faspex Dropbox
Dropboxes provide a file submission system that users can drop their packages into. dropbox members can submit files as well as view them. Admins can also invite external users (people who don’t have a Faspex account) to submit to a dropbox.
Faspex users submit files to a dropbox they have membership in by selecting the dropbox from the New Package drop-down. However, users don’t necessarily have to be a member or even a Faspex user to submit to a dropbox.
Admins can invite external users to submit to a dropbox using an emailed, private link. Admins can also distribute a public URL that allows those who access it to obtain a private link to the dropbox submission page.
IBM ASPERA FASPEX 4.4.0
HTTP Gateway
When sending a new package, users can choose whether to send with Connect or with HTTP Gateway (if HTTP Gateway is enabled). (CIM-2575)
Faspex leverages the HTTP Gateway JavaScript SDK to interact with HTTP Gateway.
You can use the HTTP Gateway service to make transfers in Faspex by providing Faspex with the URL to your HTTP Gateway server (Server > Transfer Options). (CIM-1875)
Dutch and French Localization
Localization for external user’s pages
Faspex is now in Dutch and French.
File Name Obfuscation
You can now enable file name obfuscation in Faspex (Server > Security). File name obfuscation when transferring through Connect requires Connect version 3.9.8 or higher. (CIM-1864)
Transfers
When sending a package, users can choose to prevent recipients from using HTTP (HTTP fall back or HTTP Gateway) to download the package. The recipient must use Connect to download the package.
IBM ASPERA FASPEX 4.3.1.2
Sender quotas allow Faspex admins to control the maximum volume of data that specific Faspex users can send to specific recipients over a rolling period, based on settings at the global and user account levels. For example, admins can prevent all Faspex users from individually sending more than 25 GB over a twenty-four-hour period, while allowing some of those users to send an unlimited amount of data. Sender quotas can be applied based on who is sending, who is receiving, or both. Senders and receipients can be exempted from sender quota enforcement based on their email address domain name.
IBM ASPERA FASPEX 4.3.1.1
Admins can configure global distribution lists that can be used by all users to send packages to a list of email addresses and Faspex users. Each distribution list consists of a comma-separated list of email addresses or Faspex usernames. The items in the list are not validated until a user tries to send a package to the list. Admins can configure whether all users can see these lists or whether admins have to grant access to individual users.
IBM ASPERA FASPEX 4.3.1
Metadata refers to the additional information that an IBM Aspera Faspex user can send with a file package. For example, an admin can require that, when a user sends an audio-file package to a producer, the user must also specify the sample rate, bit depth, and compression of the package. The admin sets these requirements by creating a new metadata profile that can the admin can then apply to all new, normal packages or to individual dropboxes.
IBM ASPERA FASPEX 4.3.0
Faspex automatically converts email addresses in recipient fields to existing Faspex users associated with the same email addresses. If there are multiple users associated with an email address, the address expands to all matching users. If a user exists whose username is the entered email address, the email address is not expanded and the package or notification is sent to that user only.
IBM ASPERA FASPEX 4.2.1
A patched Faspex installation displays the current patch version in the page footer, defined by a patch-version file included in a patch. Upgrading Faspex removes the patch-version file.
Aspera strongly recommends backing up your IBM Aspera Faspex configuration and database as a precaution in case of system failure. You can also choose to restore Faspex on a completely new workstation on which you’ve installed Faspex.
IBM ASPERA FASPEX 4.2.0
IBM Aspera Faspex supports Security Assertion Markup Language (SAML) 2.0, an XML-based standard that allows secure web domains to exchange user authentication and authorization data. With the SAML model, you can configure Faspex as a SAML online service provider (SP) that contacts a separate online identity provider (IdP) to authenticate users. Authenticated users can then use Faspex to access secure content.
With SAML enabled, Faspex redirects a user to the IdP sign-on URL. The user signs in with the IdP and the IdP sends a SAML assertion back to Faspex, which grants the user access to Faspex. When a SAML user logs in to Faspex for the first time, Faspex automatically creates a new user account based on the information provided by the SAML response. Any changes subsequently made to the account on the DS server are not automatically picked up by Faspex.
IBM ASPERA FASPEX 4.1.1
You can configure the primary address Faspex uses to connect with the primary Faspex node. The primary node address is the node address you provided when you installed Faspex locally or remotely
IBM ASPERA FASPEX 4.1.0
Admins can configure global distribution lists that can be used by all users to send packages to a list of email addresses and Faspex users. Each distribution list consists of a comma-separated list of email addresses or Faspex usernames. The items in the list are not validated until a user tries to send a package to the list. Admins can configure whether all users can see these lists or whether admins have to grant access to individual users