Axway Secure Client 6.2 Release Notes

New features and enhancements

Automatic site synchronization

This feature allows the user to synchronize the content of a selected remote location with a local folder. The synchronization jobs are bi-directional and can be scheduled to run at predefined periods. This feature is supported with SecureTransport server v5.3.1 or later over HTTP and HTTPS protocols.

To guarantee the normal operation of this feature, make sure that the users have full permissions over the synchronized files and folders.

Security improvements

Secure default configuration – when the user creates a new site, the default value for the connection protocol is HTTPS. By default, the only selected SSL protocol is TLS 1.2 and the less secure cipher suites are disabled.

For more information on how to setup your product, refer to the Secure Client 6.2 Security Guide, Security best practices section.

Keyboard navigation

Secure Client 6.2 is fully operable with keyboard shortcuts. A list of all keyboard shortcuts is available in the Secure Client 6.2 User Guide, Accessibility section.

Java upgrade

The bundled JRE is upgraded to Java version 8u51 to benefit from all security and performance improvements.

Support for the latest Windows and Linux platforms

Secure Client 6.2 is supported on the latest Windows and Linux platforms – Windows 10, Windows Server 2012 R2, RHEL 7, SUSE 12. Note that starting from version 6.2, the product will not be supported on AIX, Solaris and HP-UX.

More information and a list of all supported platforms are available in the Secure Client 6.2 Installation Guide, Hardware and platform requirements section.

Compatibility with the latest Axway servers

Secure Client 6.2 is fully compatible with Axway SecureTransport 5.3.1 and Axway Gateway 6.16, in addition to the other already supported server versions. Note that starting from version 6.2, we no longer commit to full interoperability with Secure Client 5.1 and Axway Gateway 6.14.

More information and a list of all supported servers is available in the Secure Client 6.2 Installation Guide, Interoperability section.

Fixed problems

Case ID Internal ID Description
718878 127502 Issue: Previously, Secure Client created a connection to the remote server, even when there were no files to upload. This opened up unnecessary connections to the server and could have potentially exhausted its resources.
Resolution: Now, Secure Client triggers the job, checks for files matching the pattern and connects to the server only if there are files to transfer.
786865 152336 Issue: Previously, there was a Null Pointer Exception when attempting to connect to SecureTransport 5.3.0 over FTP.
Resolution: Now, this issue is resolved and the content of the remote directory is listed successfully.
617303 80289 Issue: Previously, remote files with a leap date (February 29) were not correctly displayed.
Resolution: Now, the issue is resolved and the files are listed correctly over all protocols.
788814 153375

Issue: Previously, it was not possible to paste the local or remote paths.

Resolution: Now, the issue is resolved and the user can paste text in the fields for local and remote paths.

752829-1 136696 Issue: Previously, Secure Client behaved differently over HTTP and SFTP when it attempted to list a single file in batch mode.

Resolution: Now, the issue is fixed and there is no difference in the behavior over the different protocols.

786407 152096 Issue: Previously, transfers initiated by Secure Client when uploading files remained in the In Progress state on the server.

Resolution: Now, the issue is resolved and Secure Client sends all required commands to the server and the transfer state is successfully changed.

    Issue: Previously, it was not possible to change the password of a local SecureTransport user from Secure Client over SFTP and FTP(S).

Resolution: Now, the user can change their password from Secure Client. Note that over FTP(S) and SFTP, the password change should be initiated by the server administrator with the Require user to change the password on next login option.

Known issues

  • A known defect in Oracle JVM (32-bit) on Linux (64-bit) operating systems prevents scheduled tasks from handling system time changes. To resolve the problem, restart Secure Client after any system time change on Linux (64-bit) operating systems.
  • When using an old site file to update/create Gateway sites, Secure Client will return an, "Axway is not a supported server type" error.
    Workaround: Change the value of the property RemoteSrvType in your site file from AXWAY to GATEWAY.
  • Intervals between runs of scheduled recurrent jobs are not always the same. For example, if you schedule a job to execute every 3 days and the start date is 02.11.2012, the first run of the job will be on 04.11.2012. Executions will happen every 3 days, starting with the first day of every month (Nov. 1st, Nov 4th, Nov. 7th, etc). Similarly, minutely recurrent jobs execute on every X minutes starting on every round hour. Hourly recurrent jobs are executed every X hours, starting on 00:00 on every day. Monthly recurrent jobs are executed on every X months, starting from January of every year. To find when the recurrent job will be executed use the Preview button in the Schedule section.
  • If you make a change in one page of the Preferences window, it might not be reflected on other pages until you save and reopen the window. For example, if you add a proxy in the Proxies page, it does not appear in the Proxy list on the SecureTransport Compatibility page immediately.
  • When Use Windows Certificate is selected in the Security Settings and two certificates in the Windows personal store have the same friendly name (called alias in Secure Client), only one is displayed in the Security Manager. This is due to a limitation of a third-party API.
    Workaround: Use the Secure Client certificate database, and edit the aliases in the Import Certificate Wizard so that each certificate has a unique alias.
  • When Use Windows Certificate is selected in the Security Settings and a certificate is deleted in the Windows intermediately store, the changes are not displayed in the Security Manager until the Security Manager is closed and then reopened.
  • If you import a certificate that includes upper case letters in its common name (CN) using either the Import Certificate Wizard or the sclientadm addcert command, Secure Client sets the alias in its certificate database to the CN value in lower case.
  • If you import a certificate using the sclientadm addcert command and use the -alias option to specify an alias that includes upper case letters, Secure Client stores the alias in its certificate database as the value given in lower case. This does not create a problem for the sclientadm displaycert command because it uses a case-insensitive search to locate the certificate.
  • The mget command does not work properly when used with a parameter containing a range of values for Chinese characters for a filename.
  • When connected to Axway Gateway over FTP(S), Axway Secure Client displays two columns containing filename information. The second column provides additional information about that file.
  • If you choose to use an existing Java Virtual Machine (JVM) during installation, installation completes but does not use the bundled JVM. This can create problems with the uninstall and maintenance operations. The minimum required Java version is JRE 1.8.0.
  • The setstopped option of the sclientadm command is deprecated and has no effect.
  • If a delete or mget command on a Secure Client command line uses a file name pattern (with wildcard characters), the operating system applies the pattern for the local directory and the files that match the pattern in the remote directory are not deleted or transferred.
    Workaround: Enclose the file name pattern in quotation marks. This prevents the operating system from expanding the pattern so the Secure Client command can process it correctly.
  • If the file name on a delete batch command contains a dollar sign ( $), Secure Client truncates the name before the dollar sign and attempts to delete the file with the resulting name.
  • When you execute a SecureTransportclient transfer and add the progress option, an incorrect site is displayed temporarily on the Sites Manager view page. When the transfer is completed, the incorrect site will disappear.

Documentation

This section describes documentation enhancements and related documentation.

Documentation enhancements

In Secure Client 6.2, the documentation set has been enriched with a new document - Secure Client Security Guide. It provides instructions and recommendations to help you strengthen the security of the product.

Support services

The Axway Global Support team provides worldwide 24 x 7 support for customers with active support agreements.
Email support@axway.com or visit Axway Sphere at support.axway.com.

Copyright © 2015 Axway. All rights reserved

 

Related Links