Support Questions
Find answers, ask questions, and share your expertise

How To enable https port for oozie web UI.



How To enable https port for oozie web UI. 


Hi Team,


We recieved the following security vulnerability from our server team for the ports 10002 and 11000 Hiveserver and oozie web UI ports

11000 HTTP Security Header Not Detected
10002 HTTP Security Header Not Detected

We will disable HS2 port as it is not being used for anything.

We are using CDH 5.14 version. Looks like this vulnerability is fixed in the higher versions of CDH and CDP

Here is some more details about this vulnerability

"Note: To better debug the results of this QID, it is requested that customers execute commands to simulate the following functionality: curl -lkL --verbose.

CWE-693: Protection Mechanism Failure mentions the following - The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. A "missing" protection mechanism occurs when the application does not define any mechanism against a certain class of attack. An "insufficient" protection mechanism might provide some defenses - for example, against the most common attacks - but it does not protect against everything that is intended. Finally, an "ignored" mechanism occurs when a mechanism is available and in active use within the product, but the developer has not applied it in some code path.

Customers are advised to set proper X-Frame-Options, X-XSS-Protection, X-Content-Type-Options and Strict-Transport-Security HTTP response headers.

Depending on their server software, customers can set directives in their site configuration or Web.config files. Few examples are:

Apache: Header always append X-Frame-Options SAMEORIGIN
nginx: add_header X-Frame-Options SAMEORIGIN;
HAProxy: rspadd X-Frame-Options:\ SAMEORIGIN

Apache: Header always set X-XSS-Protection "1; mode=block"
PHP: header("X-XSS-Protection: 1; mode=block");

Apache: Header always set X-Content-Type-Options: nosniff

HTTP Strict-Transport-Security:
Apache: Header always set Strict-Transport-Security "max-age=31536000; includeSubDomains"
Nginx: add_header Strict-Transport-Security max-age=31536000;

Note: Network devices that include a HTTP/HTTPS console for administrative/management purposes often do not include all/some of the security headers. This is a known issue and it is recommend to contact the vendor for a solution. "

They have told to reach out to the vendor to fix the issues.

We would like to get some fix for this:



How To enable https ports for oozie web UI. It involves creating keystore file, that's why it is hard to do it.


By enabling this https will it fix this vulnerability ?


Please suggest if there is any fix available or the suggested methods would work. Please suggest the steps to do the same as well.

Thank you !