[jira] [Resolved] (IMPALA-7585) Always set user credentials after creating a KRPC proxy

["Michael Ho (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/IMPALA-7585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Ho resolved IMPALA-7585.
--------------------------------
       Resolution: Fixed
    Fix Version/s: Impala 3.1.0

> Always set user credentials after creating a KRPC proxy
> -------------------------------------------------------
>
>                 Key: IMPALA-7585
>                 URL: https://issues.apache.org/jira/browse/IMPALA-7585
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Distributed Exec
>    Affects Versions: Impala 3.0, Impala 2.12.0
>            Reporter: Michael Ho
>            Assignee: Michael Ho
>            Priority: Major
>             Fix For: Impala 3.1.0
>
>
> {{kudu::rpc::Proxy}} ctor may fail in {{GetLoggedInUser()}} for various reason:
> {noformat}
> Error calling getpwuid_r(): No such file or directory (error 2). 
> {noformat}
> This resulted in an empty user name being used in {{kudu::rpc::ConnectionId}}. With plaintext SASL (e.g. in an insecure Impala cluster), this may result in the following error:
> {noformat}
> Not authorized: Client connection negotiation failed: client connection to 127.0.0.1:27000: SASL(-1): generic failure: All-whitespace username.
> {noformat}
> While one can argue that Kudu should fall back to some default username (e.g. "cpp-client") when {{GetLoggedInUserName()}} fails, it may have non-trivial consequence (e.g. generating an authn token with some random username on one machine while using the real user name on another machine). Therefore, it's best for Impala to explicitly set the user credentials (impala/<some-hostname>) after creating the proxy.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)