This release focuses on several security related that were reported by users. In this release a new constraint has been introduced to limit the spaces from which a profile can be used. This reduces the risk of malicious use of the database profiles.

The class loader code had an incompatibility with Java 11 that has been fixed.

In the driver configuartion sections, added a comment about needing to match the driver version with the running jvm version. Added some code to print out the present jvm version and bits for convienence.

In earlier versions, if a user entered an invalid jdbc driver path, such as "//JdbcDrivers" on a Windows host, it would crash the configuration page and prevent it from being fixed. This error is now trapped so the configuration page will load and the invalid path can be fixed.

Confluence 7.0 Compatibility

For reasons still not understood, IE does not seem to be able to use jQuery to traverse the xml containing the saved configuration information. If an admin uses IE to try and updated the settings, they could overwrite the old settings without knowing it. Several days were spent trying to fix the issue - but it seems to be buried deeply in the jQuery library. In order to as least prevent data loss, I warning is posted when the saved configurations cannot be loaded and the buttons to save data are also disabled. Definitely not the ideal situation, but better than allowing the accidental data loss.

This was requested by a user.

Prior to this release, connection profiles to Oracle were not working correctly.

Fixed the Data Center functionality for the Macro Results Cache macro.

This version provides an option in the Database Query and Database Query Compact macros to cache results. There is also a new macro for caching results. The Macro Results Cache has some potential issues in a Confluence Data Center. See the documentation for details.