IBM Aspera Enterprise Server 3.6.2

The command to resume ascp with the command-line argument k2
or k3 now works when an FIPS-140 compatible cipher is set.

Added support for tokens for parent paths in single path transfers. For example, a token
built for /general will also allow a transfer of a single file or
directory named /general/other/subsidiary.

ascp now supports multiple private SSH key files that are called on
the command line, specified with -i arguments. The keys are tried in
order and the process ends when a key passes authentication or when all keys have been
tried and have failed authentication.

Added support for encryption-at-rest (EAR) in the watchfolder configuration.

[Watchfolder] Upgrading to Enterprise Server 3.6.2 deletes all watchfolders. Workaround:
Before upgrading, locate the watchfolder identifier generated in ES 3.6.0. Do this by
opening the watchfolderd logs and locating a line similar to the
following:

In
the example above, b7520a90-86f4-4485-9178-f746c9ef98c5 is the generated
identifier. Save the identifier somewhere to access it later.

After upgrading to 3.6.2,
run the following to reload your preexisting watchfolder
configuration:

asperawatchfolderd --identifier watchfolder_id

For
example:

asperawatchfolderd --identifier b7520a90-86f4-4485-9178-f746c9ef98c5

Issues Fixed in this Release

(This release contains tickets created from two tracking systems; thus there are two
different formats for ticket identifiers.)

#WAT-230 - [watchfolderd] Post-processing is not performed for failed drops to a
watchfolder: when a drop fails because it has exceeded its configured retry period (nothing
transfers for x seconds), the post-processing for the drop is not executed and the
corresponding files do not reach a final state. The logs incorrectly show the file state
TRANSFER_FINISHED.

#WAT-223 - When creating a watchfolder with post-processing transfer_delete, the
source files are not removed after they are successfully transferred

#36291 - When uploading or downloading a file that exists at the target destination, the
transfer overwrites the file instead of skipping the transfer.

#36052 - For Point-to-Point and Client, the passwords set in Global Preferences (under the
Mail and Proxy tabs) are not saved properly.
After the software is shut down and then reopened, the admin user may find that the password
fields in Global Preferences are empty and the features requiring those passwords no longer
work. Thus, the passwords need to be recreated in the UI or in
aspera.conf each time.

Note: Because of this Known Issue in 3.6.1,
admin users upgrading from 3.6.1 to 3.6.2 may need to recreate these passwords after the
upgrade is complete.

#35893 - When a docroot is configured on a remote server and a new hot folder is configured
with a source folder equal to / (with any existing local folder as the
destination folder) the underlying ascp transfer fails because the
asperasync services removes trailing slashes from directory paths,
resulting in an empty source path.

#33872 - After installing the license, an incorrect error message is displayed: The
server has a client license.

IBM Aspera Shares On Demand (SHOD)

Shares 1.9.4 New Features

Shares now displays the account status and expiration date (if applicable) of a user on
the Users page (Admin > Accounts > Users).

The activity feed now includes items on Node API activity, including when the Node API
creates and deletes files and folders.

Shares now supports a rake task to export a share's name and directory.

Shares now supports a rake task to configure a custom logo.

Removed the requirement that SAML users must have the given_name attribute to
log in.

Shares now supports IPv6 by default. You can disable IPv6 by editing the
nginx.conf file. See the documentation for more information.

#29858 - Sometimes Console's database is left empty after restoring a configuration file
and users not allowed to log back into Console. Workaround: Before restoring your
configuration file, follow the steps in this article: https://support.asperasoft.com/entries/90334347.

OTHER RESOURCES

PRODUCT SUPPORT

For on-line support resources for Aspera products, including raising new support tickets,
please visit the Aspera Support Portal. Note that you may have an existing account
if you contacted the Aspera support team in the past. Before creating a new account, first
try setting a password for the email that you use to interact with us. You may also call one
of our regional support centers.