IBM Aspera HST Admin Manual page 300

Element
aggressiveness
server
activity_event_logging
recursive_counts Optional
aej_logging
files_filelock_enabled
files_filelock_restriction
Minimum Access Key Configuration - The Storage Object
The "storage" section requires different values, depending on the storage type. The following examples contain the
minimum information required to create an access key, and can be cut and pasted into a text file for editing.
Local storage
{"storage" : {
"type" : "local",
"path" : "path"
}}
Required Type
Optional Float
Optional JSON object
Optional Boolean
Boolean
Optional Boolean
Optional Boolean
Optional String
Description
The aggressiveness of transfers that are authorized by
this access key in claiming available bandwidth. Value
can be 0.00-1.00. Available as of 3.8.0.
The server configuration object. Available as of 3.8.0.
Set to true to allow the Node API to query transfers
that are associated with this access key through the
/events endpoint. The access key configuration
overrides the server configuration. This option must be
enabled for event reporting to IBM Aspera on Cloud.
Default is unset, such that the access key inherits the
server configuration. Available as of 3.8.0.
Set to true to enable recursive counts. The access
key configuration overrides the server configuration.
This option must be enabled for event reporting to IBM
Aspera on Cloud. Default is unset, such that the access
key inherits the server configuration. Available as of
3.8.0.
Set to true to enable reporting to the IBM Aspera
on Cloud Activity app. The access key configuration
overrides the server configuration. This option must
be enabled for activity reporting to the IBM Aspera
on CloudActivity app. Default is unset, such that the
access key inherits the server configuration. Available
as of 3.9.0.
Set to true to allow the access key user
to create filelocks. Filelocks cannot be
set if filelocks are disabled on the server
(files_filelock_enabled is set to false in
aspera.conf). Available as of 3.8.0.
Set to none to allow the access key user to write,
delete, or rename files if they are not locked or if the
filelock was applied by the user. Set to write to allow
the access key user to write, delete, or rename files
only if the filelock was applied by the user. Available
as of 3.8.0.
| Authentication and Authorization | 300