Configuring Token Authorization in aspera.conf

Requirements:
  • You have created a transfer user on your server.
  • You have set up the transfer user with an SSH public key as described in Setting Up Token Authorization.

The examples below use a transfer user called aspera_user_1.

  1. Run the following command:
    > asconfigurator -x "set_user_data;user_name,aspera_user_1;authorization_transfer_in_value,token;authorization_transfer_out_value,token;token_encryption_key,key"

    Aspera recommends that the key be a random string of at least 20 characters. This command creates the following text in aspera.conf:

    <user>
        <name>aspera_user_1</name>
        <authorization>
            <transfer>
                <in>
                    <value>token</value>
                </in>
                <out>
                    <value>token</value>
                </out>
            </transfer>
            <token>
                <encryption_key>gj5o930t78m34ejme9dx</encryption_key>
            </token>
        </authorization>
        <file_system>
              ...
              ...  
        </file_system>
    </user>

    You can also configure token-authorization settings in the <default> section to apply them globally for all users. For instructions on how to run asconfigurator commands to do so, as well as to view other token configuration options, see User, Group and Default Configurations.

  2. Optional: you can manually edit aspera.conf in a text editor with write permission.
    Open the file from the following location:

    C:\Program Files (x86)\Aspera\Point-to-Point\etc\aspera.conf

    Add text as needed to configure token authorization for the user or globally. Save your changes.

    Validate the aspera.conf file using the asuserdata utility:
    > asuserdata -v