edgeCore 4.2.2 Release Notes
Production date: August 26, 2020
The 4.2.2 release introduces new functionalities related to authentication and data management.
Authentication Database Support
Oracle is now supported as an official authentication database, and as such is used to store accounts, provisioning, and sessions.
Using Oracle for Caching
Besides the H2 and MySQL database, EdgeCore now has the ability to also use Oracle to store its cache. As a result, the memory footprint of your equipment will be reduced, and your servers can be smaller and cheaper.
- The issue where setting a group of pageVars at once from an HTML template resulted in the “Cannot call method ‘$applyAsync’ of undefined” error has now been resolved.
- The issue where you were not able to set an empty value for pageVars in actions has now been resolved. Previously, when you left the value field empty and saved the action, your settings were changed to Unset instead of being empty.
- The issue where edge.net.ssl.EdgeTrustStore.mergeKeyStores threw the Cannot store non-PrivateKeys exception has now been resolved.
- The issue where using /es-cli.sh resulted in the Cannot initialize truststore: Cannot store non-PrivateKeys error has now been resolved.
- The issue where weather overlays could not be refreshed has been resolved. Even though weather overlays were enabled in map visualizations, there was no option to refresh them, so they would get out of date within minutes.
- The issue that caused Expand to New Tab to have layout problems has been resolved.
- The issue where the saved filter state caused custom expression filter problems has been resolved. You had a custom expression filter with a number of options, and you left one selected. Upon returning to the same page with a different set of data, if the new set of data did not contain any rows that matched the previously selected (and remembered) filter setting, the visualization showed “0 of X” records. Since there was no matching data, the selected filter button was greyed out and could not be untoggled.
- It is now possible to disable the use of info.login.password expression.
The following configuration in custom / local.properties disables the said expression:
# Disable login.info.password usage.
# Never store user credentials; prompted by webData / webContent
# SSO challenge forms (one-time use for session only).
- Security header information has been removed from webData logs.
- Cache Compatibility (MySql / H2/ Oracle)
EdgeCore supports using H2 by default, but the system can be switched to use a MySQL Database or Oracle Database as the CacheDB. If an export is restored, any SQL Transforms should be reviewed, as H2 specific query syntax will need to be converted to MySQL or Oracle syntax. There is a script utility that reports some of these issues, and the script itself can be extended to report which Transforms reference syntax that requires updates.
- Custom Login Page Compatibility
Login pages built on versions prior to EdgeCore v4.1 are not compatible. An upgrade script is included to help stash custom login pages into ‘staticweb/login-pre4.1’ and the customizations will require manual migration to the new default template.
- HTML Template Visualizations
Based on the version you are upgrading from, the following issues could cause you to need a rewrite to your HTML Template Widgets:
– Due to the significant upgrade to Bootstrap 4, Glyphicons are no longer included. If you have custom HTML Templates that use them, in v3.11 they will all be empty.
– Due to the upgrade to Angular 9, HTML Templates that used AngularJS 1.x syntax will have to be rewritten.
- 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.
– Lock Timeouts: Transforms fail to run as temporary tables fail to be cleaned up.
– 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.
- Errors connecting to third-party https webdata/webcontent sources
EdgeCore fails to connect over HTTPS to backend data sources. In this case, one likely solution is to enable SNI. This is a global configuration, so on some systems it might have the opposite effect.
# — SNI Options; may need to be enabled (ENABLE_SNI=true) when connecting to third-party
https webdata/webcontent sources.