EC-329 – Upgraded Apache Tomcat (9.0.31 -> 9.0.34) to resolve regression failing to upload backups introduced in edgeCore v3.11.4.

EC-329 – Resolved an issue installing edgeCore as a service on Windows.

EC-282 – Resolved Credentials set as validation only failed to be resolved on testing connections.  Regression introduced in v3.11.1 (ES-682).

EC-389 – Resolved issue in logs where parameterized maintenance queries were failing (audit/session log cleanup).

EC-164 – The resolved issue where an admin was unable to make LDAP Domain Adapter configuration changes when an existing edgeCore Group/Role was deleted and it was referenced by the LDAP Domain Adapter’s Group Mapping.

EC-292 – Resolved issue in the Domains configuration screen where an LDAP Domain was deleted when the refresh button was selected.

EC-182 – Added additional logging statements when edge shell commands were executed to better show the import/export request originated from the ./edge.sh command line.

EC-430 – Resolved an issue when restoring a backup that did not contain a password policy.

EC-427 – Resolved an issue when restoring a backup where the ‘All Users’ group failed to be resolved causing the import to fail.

edgeCore Known Issues

Please review the following known issues:

Bootstrap 4 Updates

Due to the significant upgrade to Bootstrap 4, systems with customizations in the following areas should be tested to determine if they will require updates:

• HTML Template Visualizations
  • Example 1: Glyphicons are no longer included. If you have custom HTML Templates that used them, in v3.11 they will all be empty.
  • Example 2: EC-204 – updating theme theme=”bootstrap” to theme=”bootstrap4-1″
• Login Pages
• Themes

Common Table Expression ‘WITH’ Clauses

edgeCore uses the H2 database in support of the SQL Transforms. SQL that uses Common Table Expression (CTE) ‘WITH’ clauses have been identified as causing two issues.

1. Lock Timeouts: Transforms fail to run as temporary tables fail to be cleaned up.
2. Memory Leaks: The temporary table results are not being cleaned up properly in all instances, and it will trigger Out Of Memory on the JVM.

Contact Information