What's new?
These features have been changed or added in this release.
| Feature | Affected Components | Type of Change | Description |
|---|---|---|---|
| Compatibility with eperi sEcure Platform version 22.6.1.0 | Data Protection API | Enhancement | As of this release, the eperi sEcure Anonymized Test Data is compatible with the eperi sEcure Platform version 22.6.1.0. |
| Unveiling CSV Files | Data Protection API | Enhancement | Encrpted / tokenized CSV files can now be decrypted / detokenized directly from the admin console. |
| Role-Based Viewing Concept | Data Protection API | Enhancement | End-users can now have their own account for the Admin Console with respective permissions. |
| Feature | Affected Components | Type of Change | Description |
|---|---|---|---|
| Licensing | eperi sEcure Platform | Enhancement | Licensing of the eperi sEcure Platform has been made more robust and future-proof. In case you are not using a (Control) Cluster license yet, please contact us before upgrading. |
| Default Ignite Seed Address | eperi sEcure Platform | Enhancement | The Ignite seed address default was set to 127.0.0.1:47500..47600, please verify your configuration of Ignite accordingly. |
| Feature | Affected Components | Type of Change | Description |
|---|---|---|---|
| Multiple Header Filter in Milter | eperi Milter app | New Feature | Milter can now react to multiple filter criteria. For details and examples on how to configure this, please see Configuring the eperi Milter App in the respective product manual. |
| TLS Key Management | eperi sEcure Platform | Enhancement | TLS Keys assigned to Proxies or Solr Connections are now prevented from being deleted. |
| UI Enhancements | eperi sEcure Platform | Enhancement | Enhancements to the eperi sEcure Platform's Admin UI:
|
| Feature | Affected Components | Type of Change | Description |
|---|---|---|---|
| Default TLS Versions | eperi sEcure Platform | Enhancement | By default, TLS versions 1.0 and 1.1 as well as unsecure ciphers are no longer allowed for accessing the Admin Console. For this, the file /etc/eperi/gateway/tomcat/server.xml will be replaced or a new one will be created during update installation, if the according prompt in the installation process has been chosen. If you were using a custom certificate for the Admin Console, please refer to Upgrading to a new release and ensure that this continues to be referenced in the server.xml. This is especially important when Milter or Office Online Server are relying on this custom certificate. Instead of overwriting the server.xml, you may choose to keep the old version alternatively and remove support for old TLS versions and unsecure ciphers by adjusting the server.xml manually. |
| SDK Update | eperi sEcure Platform | Enhancement | The SDK in version 1.5 is now used, allowing for the migration of existing BG Tasks to the new mechanism. |
| Dependency Update | eperi sEcure Platform | Enhancement | The spring-boot v2.5.12 and spring-core v5.3.18 libraries which address CVE-2022-22965 are now used by the eperi sEcure Platform. |
| Feature | Affected Components | Type of Change | Description |
|---|---|---|---|
| UI Enhancements | eperi sEcure Platform | Enhancement | Enhancements to the eperi sEcure Platform's Admin UI:
|
| Gateway Health Export | eperi sEcure Platform | Enhancement | The Master Key configuration is now part of the eperi sEcure Platform Health Export. |
| eperi SDK | eperi sEcure Platform | Enhancement | The eperi SDK in version 1.4 is now used, offering the possibility for scheduling Background Tasks. |
| Feature | Affected Components | Type of Change | Description |
|---|---|---|---|
| Clear-text PDF Generation | eperi sEcure Platform | New Feature | The eperi sEcure Platform now offers an API which can be used for generating PDF files from XML-based input files (e.g. *.docx or *.xml) that contain tokenized values. |
| Dependency removal | eperi sEcure Platform | Enhancement | Netcat is no longer needed as prerequisite for eperi sEcure Platform installation. |
| Dependency update | eperi sEcure Platform | Enhancement | The log4j library v2.17.1 which addresses CVE-2021-44832 is now used by the eperi sEcure Platform. In this regard, please also take note of the compatibility with the latest Solr version introduced in the last Release of the eperi sEcure Platform. |
| Docker Images | eperi sEcure Platform | Enhancement | The size of eperi sEcure Platform Docker Images has been reduced significantly. |
| UI Enhancements | eperi sEcure Platform | Enhancement | Enhancements to the eperi sEcure Platform's Admin UI:
|
| Feature | Affected Components | Type of Change | Description |
|---|---|---|---|
| log4j Library Update | eperi sEcure Platform | Enhancement | The log4j library used by the eperi sEcure Platform has been updated to v2.16.0 to address CVE-2021-44228 and CVE-2021-45046. In this regard, please also take note of the compatibility with the latest Solr version introduced in the last Release of the eperi sEcure Platform. |
| Disclaimer Page | eperi sEcure Platform | Enhancement | The same Disclaimer Page is now used for all Adapters. |
| Gateway Health Export | eperi sEcure Platform | Enhancement | Data Protection Policies are now also included in the eperi sEcure Platform's Health Export. |
| UI Enhancements | eperi sEcure Platform | Enhancement | Enhancements to the eperi sEcure Platform's Admin UI:
|
| Feature | Affected Components | Type of Change | Description |
|---|---|---|---|
| Solr Compatibility | eperi sEcure Platform | Enhancement | The eperi sEcure Platform is now compatible with Solr v8.11.0. and Zookeeper v3.6.2. Follow these steps for Upgrading Solr and Zookeeper to the latest supported versions. For the time being, the eperi sEcure Platform is backwards compatible with the previously supported version. |
| Gateway Health Export | eperi sEcure Platform | Enhancement | Gateway Health Export now contains policy information of the existing apps. |
| Logging Enhancements | eperi sEcure Platform | Enhancement | Non-relevant stack traces in log are now prevented. |
| Tomcat Upgrade | eperi sEcure Platform | Enhancement | The automated installation packages will now ship with Apache Tomcat 9.0.54. |
| Java Upgrade | eperi sEcure Platform | Enhancement | The automated installation packages will ship with JRE 11.0.13(AdoptOpenJDK/HotSpot). |
| UI Enhancement | eperi sEcure Platform | Enhancement | Several UI enhancements have been implemented. |
| Solr Client Cache | eperi sEcure Platform | Enhancement | The Solr client cache has been improved so that it creates less concurrent connections. |
| Feature | Affected Components | Type of Change | Description |
|---|---|---|---|
| Solr Client Cache | eperi sEcure Platform | Enhancement | The Solr client cache has been improved so that it creates less concurrent connections. |
