KB Article #179173

TSIM- installation of SP/Patches signed with expired certificates

Problem

Effectively on 2017/12/12 01:59:59 EET, Axway’s Code Signing Certificate will expire, and without applying the provided solution, the installation of any SP/Patch will not start and the jar/update will be reported as invalid:

XXXXXXX is not a recognized Axway update

file: invalid signature. Wrong validity period for certificate "Axway Inc".


Resolution

In order to install any future SP/Patch after 12.12.2017, please update your Axway Installer to 4.9.0-SP8.

After applying SP8, run Installer with the AXWAY_SKIP_SP_SIGNATURE_CHECK=true environment variable. That way, signature checking is skipped:

WIN: set AXWAY_SKIP_SP_SIGNATURE_CHECK=true

LINUX: export AXWAY_SKIP_SP_SIGNATURE_CHECK=true

This is a must-do:

1 BEFORE installing Axway TSIM 3.9.1-SP12 (available no sooner than January 2018)

2 BEFORE any new installations for Axway TSIM 3.9.1 (if installations are carried out AFTER 2017/12/12 01:59:59 EET)

3 BEFORE applying any Service Packs / Patches on Axway TSIM 3.9.1 up to (and including) 3.9.1-SP11, 3.9.1-SP11.P01, 3.9.1-SP11.P02, and excluding 3.9.1-SP11.P03, 3.9.1-SP11.P04 (the later two can also work with the previous Axway Installer version: 4.9.0-SP6) (if installations are carried out AFTER 2017/12/12 01:59:59 EET)