Set up users and groups
Aspera® clients connect to HSTS by authenticating as a system user who is configured in the application. The user can also belong to a group that is configured in the application. Users and groups can be set up by running asconfigurator commands or directly editing the configuration file, aspera.conf .
Setting up transfer users HSTS 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.Setting up transfer groups Transfer settings can be applied to your system's user groups. If users within a group do not have individual transfer settings, then the group's transfer settings are applied. HSTS doesn't create user groups on the operating system for you, so you must ensure that the groups exist before adding them to your Aspera product.Configuration precedence HSTS applies configuration settings in the following order, where 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 After you configured an Aspera transfer user on HSTS , test that an Aspera client can successfully connect to HSTS and upload a file.