Configure the server from the command line
The following references describe the server settings that can be configured for HSTS by using the command line or directly editing the HSTS configuration file, aspera.conf .
aspera.conf - WebSocket configuration <server> section of aspera.conf can be used to configure the server to use the WebSocket protocol over HTTPS instead of SSH. The ascp client uses HTTPS for WebSocket only. However, the WebSocket server can be configured to use HTTP as long as a proxy is being used to stop the HTTPS server endpoint.aspera.conf - Authorization configuration <authorization> section of aspera.conf include transfer permissions and token configuration. Tokens are used by Aspera® web applications to authorize transfers between Aspera® clients and servers.aspera.conf - Transfer configuration <transfer> section of aspera.conf include: bandwidth control, transfer protocol options, content encryption requirements, encryption-at-rest, and inline validation.Controlling bandwidth usage with virtual links from the command line Setting the global bandwidth from the command line Increasing transfer performance by using an RTT Predictor aspera.conf - File system configuration <file_system> section of aspera.conf include the docroot, file permissions, file handling, filters, checksum reporting, and growing files. The absolute path, or docroot, is the area of the file system that is accessible to an Aspera transfer user. The default empty value allows access to the entire file system. You can set one global docroot and then further restrict access to the file system by group or individual user. aspera.conf - Transfer server configuration <central_server> section of aspera.conf include the network and port that asperacentral uses to process transfer requests and how to manage the asperacentral database.aspera.conf - Filters to include and exclude files ascp transfers all source files in the transfer list.Server-Side Encryption-at-Rest (EAR) HSTS , server-side encryption-at-rest (EAR) saves files on disk in an encrypted state. When downloaded from HSTS , server-side EAR first decrypts files automatically, and then the transferred files are written to the client's disk in an unencrypted state.Reporting checksums Server logging configuration for ascp and ascp4 log level. For ascp transfers, you can configure a different default log directory, log size, number of logs, and logging intensity on the server, and apply these settings globally or to specific users. For Ascp4 transfers, you can configure a default log size (Ascp4 does not support user-specific logging settings). These settings do not affect IBM Aspera Sync logging, which is configured in a different section. Out-of-transfer file validation HSTS . The transfer is reported as complete and then the validation is run. The validation script uses the Aspera® Reliable Query API to retrieve the list of files to validate and update the file status during validation. The transfer user who is transferring files to the server must be associated with Node API user credentials to use the API. These instructions describe how to associate a transfer user with Node API user credentials, create a validation script, and configure the server to use out-of-transfer file validation on files that it receives from specific transfer users, groups, or globally. Inline file validation the Aspera server GUI or aspera.conf .Inline file validation with URI