Aspera FASP Integration

Aspera Fast and Secure Protocol (FASP) Integration allows Mac and Windows Agents to upload files to a Portal server using Aspera instead of a shared storage or HTTP.

All Agents use a shared Aspera account, with the credentials stored in Portal.

Configuration in Portal


Configuration of the integration in Portal.

Aspera Node URL
Aspera Node API URL. Port number must to be included in the URL, normally Aspera Node API runs on port 9092.
API Username
The Aspera Node API and transfer username that is used by Agent clients to upload files to Aspera.
API Password
The password that Portal server uses towards Aspera Node API. The current password is never shown in the user interface. Leave empty to keep the current password.
Verify SSL
Whether Portal should verify the SSL certificate when communicating with Aspera Node API. It is recommended to verify the certificate for additional security, but this may not be possible with for example self-signed certificates.
Mounted Portal storage
The Portal storage that is mounted from the Aspera server. Root of this storage must point to the same path that “Path within Aspera” points to.
Path within Aspera

Path of selected Portal storage in Aspera, relative to the document root of the user defined in API Username.

For example: Username is agent, users document root in Aspera would by default be /transfer/agent, and if this setting is left empty, then /transfer/agent should be mounted on Portal server as a storage.

Another example: A subfolder on Aspera server is used, dedicated to this Portal system,
/transfer/agent/portal-storage. Then the Mounted Portal Storage should point to /transfer/agent/portal-storage as its root, and Path within Aspera value would be set to portal-storage.

Configuration on Aspera server

Below are high-level steps of setting up a user in Aspera. Please see Aspera documentation for more details. Links below are for Linux version of Aspera documentation.

Authentication flow

Agent authenticates against Aspera using Aspera Connect SSH key. All transfers are verified using transfer tokens. Example authentication flow when the Agent uploads files using Aspera:

  1. Agent authenticates to Portal using Portal credentials
  2. Agent asks Portal for an upload token specific for a single file
  3. Portal requests a token from Aspera Node API for this file and returns it to the Agent, along with Aspera username
  4. Agent uses the provided token, username and default Aspera Connect key, to start an Aspera transfer of the file