Configuring for Aspera Files

Aspera Connect Server, or Enterprise Server with a Connect-enabled license, must be configured to use the Aspera Node API, which is required to connect these standalone, on-premise systems to Aspera Files. The server accesses the Node API using a node API username and password, that is associated with a local system account called xfer. All transfers and system operations on the computer are run under xfer. Thus, to add a server as a Files node, on the server you must create the system user, configure it as an Aspera transfer user, associate the transfer user with a node username and password, and configure the server to work with Files. Files users access the Node API and Files nodes using access keys, which can be created on the server or in the Files UI.

System Requirements: