[
https://issues.apache.org/jira/browse/HIVE-25349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383558#comment-17383558
]
Gopal Vijayaraghavan commented on HIVE-25349:
---------------------------------------------
This looks like a security issue in the making, because this is entirely client
provided.
There is already a mechanism to do this without headers, but by configuration
based on the TCP connection origin.
{code}
HIVE_SERVER2_TRUSTED_DOMAIN("hive.server2.trusted.domain", "",
"Specifies the host or a domain to trust connections from.
Authentication is skipped " +
"for any connection coming from a host whose hostname ends with the
value of this" +
" property. If authentication is expected to be skipped for connections
from " +
"only a given host, fully qualified hostname of that host should be
specified. By default" +
" it is empty, which means that all the connections to HiveServer2 are
authenticated. " +
"When it is non-empty, the client has to provide a Hive user name. Any
password, if " +
"provided, will not be used when authentication is skipped."),
{code}
This was intended to only work inside a k8s container where this information
was secured with mutual TLS certificates already.
> Skip password authentication when a trusted header is present in the Http
> request
> ---------------------------------------------------------------------------------
>
> Key: HIVE-25349
> URL: https://issues.apache.org/jira/browse/HIVE-25349
> Project: Hive
> Issue Type: Improvement
> Components: Hive, HiveServer2
> Reporter: Sai Hemanth Gantasala
> Assignee: Sai Hemanth Gantasala
> Priority: Major
> Labels: pull-request-available, security-review-needed
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Whenever a trusted header is present in the HTTP servlet request, skip the
> password based authentication, since the user is pre-authorized and extract
> the user name from Authorization header.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
