Hardware Appliance 3.15 Release Notes
NOVEMBER 2024
The Hardware Platform team is pleased to announce the release of EJBCA Hardware Appliance and SignServer Hardware Appliance version 3.15.0.
This release brings a new updated versions of EJBCA and SignServer and enables the migration process to the new generation of the hardware appliance. The release also includes other improvements as well as error corrections.
Highlights
New versions of EJBCA Enterprise and SignServer Enterprisse
EJBCA Enterprise 9.1.1
Updated version of EJBCA Enterprise, see the EJBCA 9.1 Release Notes.
SignServer Enterprise 7.1.1
Updated version of SignServer Enterprise, see the SignServer 7.1 Release Notes.
Implementation of the Migration to the Next Generation Hardware Appliance
For detailed information, see Migration to Next Generation Hardware Appliance Version 4.
Improvements and Fixes
New Features and Improvements
The following lists improvements included in the release.
Update of MariaDB Server to 10.6.20.
Update of MariaDB Connector to 3.4.0.
Update of openSSH to 9.8.
Update to Java 17.
Update to WildFly 32.
Improvements on supporting TLS 1.3.
The number of active certificates in EJBCA is shown in WebConf and the support package.
Bug fix: allow clusters with a gap in node numbering (for example nodes 1 and 3).
Bug fix: EJBCA Webservice accessibility .
Upgrade Information
It is recommended to create a backup before upgrading.
Appliances with hardware version 4.x, should not be downgraded to a firmware version prior to 3.13.1.
Appliances with hardware version 2.5 with a purple front bezel should not be downgraded to a firmware version prior to 3.12.1.
A running/installed system with 3.13.0 or higher (updated MariaDB) should not be downgraded to a version prior to 3.13.0 (as the DB will then be incompatible).
Important Notice
As of firmware version 3.13.0, downgrading from WebConf to version 3.12.1 or any earlier version is no longer supported.
For more information, refer to the Upgrade Notes.As of version 3.14.0, link bonding is not offered anymore in WebConf. For customers who are currently using this feature, you would be able to continue using it.