Testing the Web UI

Follow the steps below to test your Aspera Connect client transfers through the Web UI.

Note: The instructions require steps to be taken on both the Connect Server machine and a client computer. Make sure that you are performing the steps on the correct machine.
  1. Configure an Aspera transfer user on the Connect Server.

    Set default values to authorize transfers in and out, set the encryption key, and set the default docroot by running the following commands:

    $ asconfigurator -x "set_node_data;authorization_transfer_in_value,allow"
    $ asconfigurator -x "set_node_data;authorization_transfer_out_value,allow"
    $ asconfigurator -x "set_node_data;token_encryption_key,token_key"
    $ asconfigurator -x "set_node_data;absolute,docroot"

    These commands create the following lines in aspera.conf. In the example, the encryption key is secRet (rather than the random string of at least 20 characters as recommended by Aspera) and the docroot is /sandbox/$(name). By using the substitutable string $(name) in the docroot, the application automatically replaces it with the login user name.

    <CONF version="2">
       ...
       <default>
        <authorization>
           <transfer>
            <in>
              <value>allow</value>
            </in>
            <out>
              <value>allow</value>
            </out>
          </transfer>
          <token>
            <encryption_key>secRet</encryption_key>
          </token>
        </authorization>
        <file_system>
          <access>
            <paths>
              <path>
                <absolute>/sandbox/$(name)</absolute>
              </path>
            </paths>
          </access>
        </file_system>
        ...
       </default>
    </CONF>

    To add the settings to aspera.conf manually, open it from the following directory:

  2. Configure Apache authentication for the system user on the Connect Server.
    In addition to SSH authentication, Connect Server uses Apache's authentication to authorize Web UI access. To set up a system user (asp1 in this example) for Apache authentication, run the htpasswd command below.
    Note: On the first run of htpasswd, you must use the -c option to create the file for credential storage, webpasswd. Do not use the -c option otherwise.
    $ /opt/csw/apache2/sbin/htpasswd /opt/aspera/etc/webpasswd asp1
  3. Test the Web UI with the client machine
    The client machine must be running a supported operating system and browser, as described in Requirements, and cookies must be enabled in the client's browser.

    Go to the following address in the browser:

    HTTP http://server_ip_or_name/aspera/user
    HTTPS https://server_ip_or_name/aspera/user

    The Aspera Connect browser plugin banner appears with a link to download and install the latest version of Connect:

    Click Download latest version.

    Once the installation is complete, refresh the page and the Web UI for Connect Server appears:

    In the Web UI, click Upload and select one or more files to upload to Connect Server. When the transfer is finished, select the uploaded files in the Web UI, and click Download.

    Note: When you add files to the Web UI, do not use the following characters in the filenames:
    / \ " : ' ? > < & * |

    For more information about the Aspera Connect browser plugin, see the Aspera Connect User Guide.

If you cannot initiate FASP transfers by using the Web UI, see Clients Can't Establish Connection.