You are viewing a plain text version of this content. The canonical link for it is here.

Posted to common-issues@hadoop.apache.org by "Steve Loughran (JIRA)" <ji...@apache.org> on 2016/02/01 20:40:39 UTC

[jira] [Updated] (HADOOP-12754) Client.handleSaslConnectionFailure() uses wrong user in exception text

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

Steve Loughran updated HADOOP-12754:
------------------------------------
    Attachment: HADOOP-12754-001.patch

switch to log current user, i.e. whoever is actually trying to make the call that just failed

> Client.handleSaslConnectionFailure() uses wrong user in exception text
> ----------------------------------------------------------------------
>
>                 Key: HADOOP-12754
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12754
>             Project: Hadoop Common
>          Issue Type: Sub-task
>          Components: ipc, security
>    Affects Versions: 2.7.2
>            Reporter: Steve Loughran
>         Attachments: HADOOP-12754-001.patch
>
>
> {{Client.handleSaslConnectionFailure()}} includes the user in SASL failure messages, but it calls {{UGI.getLoginUser()}} for its text. If there's an auth problem in a {{doAs()}} context, this exception is fundamentally misleading



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)