IBM Aspera HST Admin Manual page 37

Settings
Configuration Precedence
aspera.conf - Authorization Configuration
page 40
aspera.conf - Transfer Configuration
42
aspera.conf - File System Configuration
63
You can also manually edit aspera.conf with a text editor.
/opt/aspera/etc/aspera.conf
Add the following section to aspera.conf:
<?xml version='1.0' encoding='UTF-8'?>
<CONF version="2">
<aaa>
<realms>
<realm>
<users>
... <!-- user-specific settings -->
</users>
<groups>
<group> <!-- Each group tag contains a group's profile. -->
<name>aspgroup</name> <!-- The group name. -->
<precedence>0</precedence> <!-- Group precedence. -->
<authorization>...</authorization> <!-- Authorization settings. -->
<transfer>...</transfer> <!-- Transfer settings. -->
<file_system>...</file_system> <!-- File System settings. -->
</group>
<group>
... <!-- Another group's settings-->
</group>
</groups>
</realm>
<realms>
</aaa>
...
</CONF>
4. Verify your configuration.
When you have finished updating the group's settings in aspera.conf, use the following command to verify it
(in this example, verify the group asp-group's settings):
# /opt/aspera/bin/asuserdata -g asp-group
5. Restart asperanoded and asperacentral to activate your changes.
Run the following commands to restart asperanoded:
# systemctl restart asperanoded
or for Linux systems that use init.d:
# service asperanoded restart
Run the following command in a Terminal window to restart asperacentral:
# systemctl restart asperacentral
Description
on page 38 When a user is a member of multiple groups, the precedence
setting can be used to determine priority.
on Connection permissions, token key, and encryption
requirements.
on page Incoming and outgoing transfer bandwidth and policy
settings.
on page Docroot, file and directory creation, access permissions,
block sizes, and so on.
| Set up Users and Groups | 37