IBM Aspera HST Admin Manual page 32

<https_port>8443</https_port>
</http_server>
</CONF>
4. Set a token encryption key.
If HTTP/HTTPS fallback is enabled, a token encryption key is required. If HTTP/HTTPS is configured without
the encryption key, initiating a transfer with the download button generates the following error:
Error: internal error - unable to start token generation
The token encryption key is the secret text string used for authorizing transfers configured to require a token.
Aspera recommends setting a key string at least 20 random characters long.
To set the token encryption key in aspera.conf, run the following command:
$ asconfigurator -x "set_node_data;token_encryption_key,secret_string"
The key should be a string of random characters, at least 20 recommended. This adds or updates the
<encryption_key> value in the <authorization> section:
Important: After changing your Aspera token settings—either in aspera.conf or the GUI—you must restart
asperahttpd. For instructions, see the last step in these instructions.
5. If you manually edited aspera.conf, validate your updated configuration file:
$ /opt/aspera/bin/asuserdata -v
6. After enabling HTTP fallback and setting a token encryption key, restart asperacentral, asperanoded, and
asperahttpd.
Run the following command in a Terminal window to restart asperacentral:
# systemctl restart asperacentral
or for Linux systems that use init.d:
# service asperacentral restart
Run the following commands to restart asperanoded:
# systemctl restart asperanoded
or for Linux systems that use init.d:
# service asperanoded restart
Run the following commands to restart asperahttpd:
# systemctl restart asperahttpd
or for Linux systems that use init.d:
# service asperahttpd restart
| Set up the HST Server Web UI | 32