IBM Aspera HST Admin Manual page 299

Element Required
policy Optional
target_rate_kbps Optional
target_rate_cap_kbps Optional
content_protection_secret Optional
preserve_timestamps Optional
Type Description
• none - require unencrypted transfers (not
recommended).
• aes-128, aes-192, or aes-256 - allow
transfers that use an encryption cipher key that is
as long or longer than the setting. These settings
use the CFB or GCM mode depending on the client
version and cipher requested. Supports all client
versions.
• aes-128-cfb, aes-192-cfb, or aes-256-
cfb - require that transfers use the CFB encryption
mode and a cipher key that is as long or longer than
the setting. Supports all client versions.
• aes-128-gcm, aes-192-gcm, or aes-256-
gcm - require that transfers use the GCM
encryption mode introduced in version 3.9.0 and a
cipher that is as long or longer than the setting.
For more information about server cipher
configuration, see
Configuration
String The policy allowed for transfers that are authorized by
this access key. Value can be high, regular, fair,
low, trickle, or fixed. Aspera recommends
against setting the policy to fixed, which can result
in the transfer rate exceeding network or storage
capacity if the client also requests a high minimum
transfer rate that is not capped by the server. This can
decrease transfer performance and cause problems on
the target storage. To avoid these problems, set the
allowed policy to fair. Available as of 3.8.0.
Integer The default initial rate for transfers that are authorized
by this access key, in kilobits per second. Available as
of 3.8.0.
Integer The maximum target rate for transfers that are
authorized by this access key, in kilobits per second.
Available as of 3.8.0.
String Provide a password to require that content be encrypted
by the client (enforce client-side encryption-at-rest)
for transfers that are authorized by this access key.
Available as of 3.8.0.
Boolean Set to true to preserve file access and modification
timestamps for transfers that are authorized by this
access key. The server configuration overrides the
access key configuration. Timestamp support in
object storage varies by provider; consult your object
storage documentation to determine which settings are
supported. Default is unset, such that the access key
inherits the server configuration. Available as of 3.8.0.
| Authentication and Authorization | 299
aspera.conf - Authorization
on page 40.