Axway Electronic Signature 2.12 Release Notes

Document version: 2 February 2021

New features and enhancements

Electronic Signature 2.12 is classed as a Long Term Update in the Axway product life-cycle.

Interoperation with standalone EBICS Client 1.1

Electronic Signature 2.12 is designed to interoperate with the standalone EBICS Client 1.1. These two products used together enable the deployment of a complete "EBICS for corporate" platform, providing electronic signature of payments, EBICS-T and EBICS-TS protocol support, monitoring and visibility of exchanges. For this interoperability, Electronic Signature relies on a rest API for the exchange of configuration data and on JMS (Apache ActiveMQ) and a shared file system for requesting payment emissions and getting EBICS acknowledgements (PSR).

Increased security

This version of Electronic Signature provides a higher level of security. The main security evolutions are listed here.

  • No default keystore/truststore
    For increased security, this release of Electronic Signature is not delivered with a default keystore or truststore with a fixed password. The first time that you run the Configuration tool, Electronic Signature generates a default TLS certificate. This certificate is self signed and has a short validity period (one month). Unlike earlier versions of Electronic Signature, the format of the keystore and truststore files is now PKCS #12. These files are now stored in the <Electronic Signature install dir>/data/cert/ directory.
  • Latest JRE releases are embedded
    Electronic Signature 2.12 is packaged with JRE 8.232.09.
    The Electronic Signature agent is packaged with JRE 11.0.5.
  • Support of PassPort 4.6.0 SP20
    The Electronic Signature 2.12 truststore contains the root certificates for Axway PassPort 4.6.0 SP20.

Fixed issues

This section lists issues specifically resolved in this release.

Case ID Internal ID Description

01063592
01087158

RDESIGN-1951
RDESIGN-1970

Issue: Same file sent multiple times. This error occurred if the PSR had no status.

Resolution: A null pointer exception in the product has been fixed so that the file will be sent only once.

01067614 RDESIGN-1956

Issue: Configuration related to the keystore and truststore in Electronic Signature should be similar to configuration options available in EBICS Client.

Resolution: Previous versions of Electronic Signature provided a default keystore and truststore with default passwords. In this version of Electronic Signature, the user provides passwords for the keystore and truststore during the initial configuration. The user can update the passwords if required, again using the Configuration tool.

01068474 RDESIGN-1959

Issue: Installation problems for some existing customers, depending on the OS. In certain cases, when a user's licence only supported the T protocol, and the user was previously using an older version of Electronic Signature, the installation process did not offer all the required configuration screens. An UndefinedVariableException was thrown by the installer.

Resolution: Fixed.

01075184 RDESIGN-1969

Issue: Retries after a network issue. This happens when an error message to be stored in the database is too long, which provokes a rollback in the handling of the message. This rollback causes a loop in the code that makes Electronic Signature repeatedly try the same operation.

Resolution: Rejection comments and error messages are now truncated to avoid this type of database error.

01100642 RDESIGN-1983

Issue: Unhelpful error messages related to PSR failures. If a PSR file was submitted with an incorrectly-formatted filename, Electronic Signature generated error messages that included Unexpected Error, PsrParsingOperation, and ArrayIndexOutOfBoundsException.

It is important that PSR files respect a specific filename convention so that Electronic Signature can detect which parser to use according to the file format:

BANKS#CUSTS#FDL.camt.002.001.02.ara#whatever.xml

The fileformat (FDL.camt.002.001.02.ara in this example) must be in the third position. #whatever is optional and is ignored by Electronic Signature.

Resolution: The error messages related to PSR have been improved so that they are more meaningful.

01100962 RDESIGN-1981

Issue: Electronic Signature occasionally stops handling incoming files. This intermittent behavior only happens in rare cases. The log reports that a NullPointerException was encountered. One workaround was to restart Electronic Signature.

Resolution: Fixed.

RDESIGN-1942

Issue: PassPort certificates expired on 09 August 2019 (PassportSSOCA) and on 28 November 2019 (PassportCA).

Resolution: Fixed. Added the new PassPort root certificates as trusted in the Electronic Signature PassPort truststore, keeping the old ones for existing objects.

IMPORTANT: This fix only applies to new installations. If you are upgrading from an older version of Electronic Signature, you must update the certificates manually. Refer to the Knowledgebase article "How to manually update Electronic Signature certificates after PassPort 2019 certificate renewal" on the Axway Support site at https://support.axway.com/kb/180325.

Known issues

Case ID Internal ID Description
01119178 RDESIGN-1996

Issue: null pointer exception occurs during installation on Linux. The error message contains "java.lang.NullPointerException at sun.awt.FontConfiguration.getVersion". This error is caused by a missing font configuration file, which is not included with the Linux version of AdoptOpenJDK. Note that the fonts themselves are present, but not the configuration file.

Workaround: Install the fontconfig package on your system.

Adobe Flash Player end of life

On 31 December 2020, Adobe stopped the support and distribution of Flash Player. New versions of web browsers no longer support Flash Player from this date. Electronic Signature 2.12 however still requires Flash.

Recommended solution

  • Upgrade to Electronic Signature version 2.13. This new version uses an HTML5-based interface and does not require Flash Player.

Alternative, temporary solutions

As a temporary solution, you can use one of the following workarounds to continue to use Electronic Signature 2.12:

  1. Make sure your web browser allows you to run Flash Player after 31 December 2020 and block automatic updates.
    • Check the version of the Flash Player plugin that you are currently using. The highest version you should use is 32.0.0.371. Later versions will no longer work after 31 December 2020.
    • If you are running a higher version, downgrade to 32.0.0.371. Freeze your configurations and environments to avoid any accidental update of the Flash Player plugin and the associated web browsers.
  2. Use the Axway Desktop Client packaged solution, that links to your pepflashplayer.dll (version 32.0.0.371 or below). This will allow you to continue to use Electronic Signature. For details, refer to the Axway Desktop Client User Guide (restricted content — login required).
  3. Purchase your own Flash Player license from Harman.

If in any doubt, contact Axway Support for advice.

Documentation

Electronic Signature documentation set

The Electronic Signature 2.12 documentation set includes the following documents:

The following reference documents are available on the Axway Documentation portal at https://docs.axway.com

  • Axway Supported Platforms
  • Lists the different operating systems, databases, browsers, and thick client platforms supported by each Axway 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 Support at https://support.axway.com.

 

Related Links