Fixed issues
These issues have been fixed in this release.
| Affected Components | Description |
|---|---|
| eperi sEcure Platform | A configured advanced setting can now be deleted and added again without refreshing the screen. |
| eperi sEcure Platform | After editing an app, the changes are visible without a manual screen refresh. |
| eperi sEcure Platform | After successfully changing Solr settings, reopening the dialog to confirm the changes now reveals the new settings as expected. |
| eperi sEcure Platform | After successfully changing settings in the eperi sEcure Admin Console, reopening the dialog to confirm the changes now reveals the new settings as expected. |
| eperi sEcure Platform | Resolved an issue that was preventing the eperi sEcure CLI Tool from starting. |
| eperi sEcure Platform | Updated the MariaDB connector to version 3.5.6 to ensure compatibility with JRE 21. |
| eperi sEcure Platform | Updated the Oracle JDBC Driver to (Ojdbc17) version 23.26.0.0.0 to ensure compatibility with JRE 21. |
| eperi sEcure Platform | Resolved a performance issue with how RewritingRules for email addresses is implemented. |
| eperi sEcure Platform | Fixed a potential security issue by ensuring that only users with appropriate permissions can access or download the Health Export. |
| eperi sEcure Platform | When a new token profile is created on an eperi sEcure Platform node that is part of a cluster, the new token profile will now be replicated to the other nodes without having to restart the eperi sEcure Platform service. |