Axway Secure Client 6.3 Release Notes

New features and enhancements

Security improvements

Sensitive data security is improved by using more secure encryption algorithm.

Secure Client detects unauthorized modifications to security settings and warns the user to take proper actions. Recovery procedure is provided in this case.

Secure Client detects unauthorized download path manipulation and warns the user to take proper actions.

New strong TLS 1.2 cipher suites are supported.

For more information, refer to the Axway Secure Client 6.3 Security Guide.

Usability and accessibility improvements

Secure Client user interface is aligned with Section 508 US Government standard.

File and folder names are pre-populated for rename actions.

Configuration improvements

Scheduler's collect unused collection delay default value is increased to 90 seconds.

Network connection read timeout is now configurable via a setting in Connection preferences.


During upgrade, Secure Client users can change selected Java Virtual Machine settings.

Secure Client 6.1 to Secure Client 6.3 direct upgrade path is provided.

Java upgrade

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

Third-party components upgrade

Jakarta-log4j, Terracota Quartz, Security Builder and Maverick J2SSH components are upgraded to the latest versions in order to benefit from all security and performance improvements.

Compatibility with desktop architecture

64-bit version of Secure Client 6.3 for Linux is now available.

Compatibility with the latest Axway servers

Secure Client 6.3 is fully compatible with Axway SecureTransport 5.3.3, in addition to the other already supported server versions.

More information and a list of all supported servers are available in the Axway Secure Client 6.3 Installation Guide, "Interoperability" section.

Fixed problems

Case ID Internal ID Description
823090 110140

Issue: Previously, Secure Client created MKDIR tasks for directories transferred via scheduled jobs, regardless of whether the directory existed on the remote side.
Resolution: Now, Secure Client will create MKDIR tasks for directories transferred via scheduled jobs, but only if the remote directory is missing at the time of execution. If the save or upload directories are missing at the time of execution, the job will fail.

830688 104735

Issue: Previously, the Secure Client user interface would freeze when working with directories that contained large amounts of files.
Resolution: Now, Secure Client user interface does not freeze and shows visual indicators for time consuming operations.

820869 102726

Issue: Previously, transfer files in TEXT mode (ASCII) that contained $ special characters and CR were corrupted.
Resolution: Now, with an upgrade to a third-party component, transfers are successful.

818666 102518

Issue: Previously, an authentication popup message for a failed login would freeze the client, preventing subsequent jobs from processing.
Resolution: Now, when "disabled authentication dialog for recurring jobs" option is set, all jobs continue to process even after a failed login.

832721 105754

Issue: Previously, the Secure Client User Guide instructions for changing the server password was confusing.
Resolution: Now, the information in the User Guide is more detailed, specifying environment requirements and expected results.

835098 104986

Issue: Previously, the Secure Client installer contained commons-logging-0.2 and commons-discovery-1.04 libraries that were not used by the product. In some cases, these libraries were triggering false vulnerability alerts.

Resolution: Now, Secure Client does not install commons-logging-0.2 and commons-discovery-1.04 libraries.

Known issues

  • A known defect in Oracle JVM (32-bit) on Linux (64-bit) operating systems prevents scheduled tasks from handling system time changes.
    Workaround: 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.
    Workaround: 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.
    Workaround: None.
  • When Use Windows Certificate is selected in 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 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.
    Workaround: None.
  • 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.
    Workaround: None.
  • 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.
    Workaround: None.
  • The mget command does not work properly when used with a parameter containing a range of values for Chinese characters for a filename.
    Workaround: None.
  • When connected to Axway Gateway over FTP(S), Secure Client displays two columns containing filename information. The second column provides additional information about that file.
    Workaround: None.
  • 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.
    Workaround: The minimum required Java version is JRE 1.8.0.
  • 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.
    Workaround: None.
  • When you execute a SecureTransport client transfer and add the progress option, an incorrect site is displayed temporarily on the Sites Manager view page.
    Workaround: When the transfer is completed, the incorrect site will disappear.
  • The setstopped option of the sclientadm command is deprecated and has no effect.

Related documentation

Go to Axway Sphere at to find all documentation for this product version.

  • Axway Secure Client 6.3 Installation Guide
  • Axway Secure Client 6.3 User Guide
  • Axway Secure Client 6.3 Security Guide
  • Axway Secure Client 6.3 Administrators Guide

Support services

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

Copyright © 2016 Axway. All rights reserved


Related Links