Description
In the enclosed spreadsheet, it shows the list of web applications deployed by Hadoop, and filters applied to each entry point.
Hadoop web protocol impersonation has been inconsistent. Most of entry point do not support ?doAs parameter. This creates problem for secure gateway like Knox to proxy Hadoop web interface on behave of the end user. When the receiving end does not check for ?doAs flag, web interface would be accessed using proxy user credential. This can lead to all kind of security holes using path traversal to exploit Hadoop.
In HADOOP-16287, ProxyUserAuthenticationFilter is proposed as solution to solve the web impersonation problem. This task is to track changes required in Hadoop code base to apply authentication filter globally for each of the web service port.
Attachments
Attachments
Issue Links
- breaks
-
HDFS-14845 Ignore AuthenticationFilterInitializer for HttpFSServerWebServer and honor hadoop.http.authentication configs
- Resolved
-
HADOOP-18666 A whitelist of endpoints to skip Kerberos authentication doesn't work for ResourceManager and Job History Server
- Resolved
-
HADOOP-16972 Ignore AuthenticationFilterInitializer for KMSWebServer
- Resolved
- causes
-
HADOOP-16356 Distcp with webhdfs is not working with ProxyUserAuthenticationFilter or AuthenticationFilter
- Resolved
-
HADOOP-16367 ApplicationHistoryServer related testcases failing
- Resolved
-
HDFS-15860 Standby Namenode bootstrap fails due to custom authentication handler being run for /imagetransfer endpoint
- Open
- is related to
-
HADOOP-16354 Enable AuthFilter as default for WebHdfs
- Resolved
- relates to
-
HDFS-14609 RBF: Security should use common AuthenticationFilter
- Resolved
-
HDFS-14730 Remove unused configuration dfs.web.authentication.filter
- Resolved
-
HDFS-15271 Remove obsolete SPNEGO configuration of NN, SNN and JN.
- Open