Fixed issues
These issues have been fixed in this release.
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | Licensing in offline mode was sometimes not possible for freshly installed Gateways. |
| eperi sEcure Platform | In the new UI, a Proxy restart was not suggested after (un-)assigning Apps. |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | Some Background Indexing tasks got stuck and had to be deleted from the database to abort them. |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | Custom TLS certificate assignment to Proxies resulted in unrelieable behavior, e.g., TLS could no longer be enabled/disabled for Proxies once a custom certificate was assigned or TLS certificates were switched to default again once TLS was enabled. |
| eperi sEcure Platform | Imported trusted certificates could not be deleted. |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | A database migration for MySQL was causing trouble during update installation. However, MariaDB was not affected by this issue. |
| eperi sEcure Platform | Clicking on Test Connection under Solr tab redirected to the logout page of the new UI |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | Custom TLS certificate assignment to Proxies resulted in unrelieable behavior, e.g., TLS could no longer be enabled/disabled for Proxies once a custom certificate was assigned or TLS certificates were switched to default again once TLS was enabled. |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | Proxies could not be edited via Quick Links. |
| eperi sEcure Platform | When the database connection was lost by the Gateway, an incorrect error message was displayed in the new UI. |
| eperi sEcure Platform | The licensing status was sometimes not displayed or displayed incorrectly. |
| eperi sEcure Platform | The eperi sEcure Platform no longer attempts to start already deleted Proxies after a eperi sEcure Platform restart. |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | Sometimes, an old version a library was not deleted when upgrading the eperi sEcure Platform. |
| eperi sEcure Platform | When upgrading from an old release of the eperi sEcure Platform to a new version, under some conditions, a unique constraint violation could appear when using Oracle as configuration database type. |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | If Oracle is the selected type of Configuration Database for the eperi sEcure Platform, a unique constraint violation could cause a eperi sEcure Platform upgrade failure with certain eperi sEcure Platform versions. |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | When creating a Forward Proxy in the new UI, additional authentication is no longer enabled by default. |
| eperi sEcure Platform | Remote Host detection is now logged including its real IP address. |
| eperi sEcure Platform | Generic decryption was improved for Date(time) Tokens. |
| eperi sEcure Platform | If there are legacy Keys inside the Gateway's database without any Certificates, the REST API now returns an empty list for the Certificates accordingly, preventing errors in the UI. |
| eperi sEcure Platform | Logging of coherent messages regarding email modifications has been improved. |
| eperi sEcure Platform | Handling of session expiration in the Admin Console has been enhanced. |
| eperi Milter app | Support for chained addresses, separated by semicolon was added. |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | Logging of coherent messages regarding email modifications has been improved. |
| eperi sEcure Platform | Handling of session expiration in the Admin Console has been enhanced. |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | Token repository is no longer stuck in a loop if a token profile runs out of tokens. |
| eperi sEcure Platform | UI enhancements |
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | It's no longer possible to delete running Proxies which led to erroneous states |
| eperi sEcure Platform | During detokenization of Dates Milliseconds are not truncated anymore |
| eperi sEcure Platform | Added a popup displaying an error in case a proxy was started without a valid license |
