Configure HSTE in
the GUI
The following references describe the server settings that can be configured in the HSTE GUI. Not all settings
are available in the GUI; some must be set by using the command line or directly editing the HSTE configuration file,
aspera.conf .
Docroot, file permission, and growing files configuration
The Docroot configuration options include the docroot and the file permissions. 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 individual user.
Authorization configuration
The Authorization configuration options include connection permissions, token key, and encryption requirements.
Server-Side Encryption-at-Rest (EAR)
Bandwidth configuration
The Bandwidth configuration options include target transfer rates, transfer policies, and assigning Vlinks to control aggregate bandwidth usage.
Controlling bandwidth usage with Virtual Links in the GUI
FASP transfers attempt to transfer at the maximum transfer rate available. However, too many simultaneous transfers can overwhelm your storage or leave little bandwidth available for other network activity. To set a bandwidth cap on the total bandwidth that is used by incoming or outgoing transfer sessions initiated by all users, or sets of specific users, set up a virtual link (Vlink).
Network configuration
The Network configuration options include the network IP, port, and socket buffer settings.
File handling configuration
The File Handling configuration options include file block size, overwrite rules, symbolic link handling, and filtering patterns.
Configuring inline file validation
If an executable file that contains malicious code is uploaded to the server, the malicious code can later be run by an external product that integrates with an Aspera product. Inline file validation is a feature that enables file content to be validated while the file is in transit, and when the transfer is complete. The validation check can be made with a REST call to an external URL. The mode of validation used (URL) and the timing of the check are set in the Aspera server GUI or aspera.conf .
Configuring filters to include and exclude files
For example, on Windows FAT or NTFS (or directories) to transfer by indicating which to skip or include based on name matching. When no filtering rules are specified by the client, ascp transfers all source files in the transfer list.
Reporting checksums
File checksums are useful for troubleshooting file corruption to determine at what point in the transfer file corruption occurred. Aspera servers can report source file checksums that are calculated in real time during transfer and then sent from the source to the destination.
Transfer server configuration
HSTE uses asperacentral to handle transfer requests from Aspera clients. You can configure server properties and behavior in the Transfer Server options, including specifying the address, enabling persistent storage, and controlling how to handle empty files.