Set up Users

Aspera clients connect to HSTE by authenticating as a system user who is configured in the application. Users can be set up in the HSTE GUI.

Setting Up Users
HSTE uses system accounts to authenticate connections from Aspera clients. The system users must be added and configured as Aspera transfer users before clients can browse the server file system or run FASP transfers to and from the server. When creating transfer users, you can also specify user-specific settings, such as transfer bandwidth, docroot, and file handling. User configuration is an important part of securing your server.
Configuration Precedence
applies configuration settings in this order: 1) user settings, 2) group settings (and if a user belongs to more than one group, precedence can be set for each group), 3) global settings, 4) default settings. User settings have the highest priority and default the lowest.
Setting Up a User's Public Key on the Server
Public key authentication is an alternative to password authentication, providing a more secure authentication method that allows users to avoid entering or storing a password, or sending it over the network. An Aspera client generates a key pair (a public key and a private key) on the client computer and provides the public key to the administrator of the remote Aspera transfer server. The server administrator sets up the client user's public key as described in the following steps.
Testing a User-Initiated Remote Transfer
Once you have configured an Aspera transfer user on HSTE, test that an Aspera client can successfully connect to HSTE and upload a file.

Parent topic: High-Speed Transfer Endpoint Admin Guide for zLinux