Fixed Issues in Apache Oozie
Review the list of Oozie issues that are resolved in Cloudera Runtime 7.2.12.
- CDPD-28080: [web UI] Oozie web UI should not serve image from http://extjs.com/s.gif.
- OOZIE-3431: Oozie web UI should not serve image from http://extjs.com/s.gif. This issue is now resolved.
- CDPD-26335: Oozie server startup error when JDBC URL for a MySql DB with HA is used.
- Oozie did not accept a JDBC url if it contained special characters (e.g.: comma or curly brackets). This is fixed now so Oozie should accept special urls, for example a MySQL HA JDBC url where you typically use comma(s). This issue is resolved.
- CDPD-24942: Add a --insecure like parameter to Oozie client so it can ignore certificate errors.
- The Oozie client now has a --insecure option which behaves like the curl command's --insecure parameter. With this there's no need to specify the -Djavax.net.ssl.trustStore and -Djavax.net.ssl.trustStorePassword parameters when SSL is enabled. This issue is now resolved.
- CDPD-27661: Implement a way to disable the Oozie UI.
- OOZIE-3431: There is a new property named "oozie.ui.enabled" users can set for Oozie with a value true of false. By default it's set to true. When set to false, the Oozie UI will be complete disabled, the Oozie server will not even expose the UI resources, hence this can be a workaround for the JQuery vulnerabilities. This issue is now resolved.
- CDPD-25864: Support basic authentication in Oozie's callback and notification url.
- Oozie's notification mechanism now supports the https://user:password@host:port/... format so it's capable of handling basic authentication. This issue is now resolved.
Apache patch information