[
https://issues.apache.org/jira/browse/HADOOP-12754?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15297669#comment-15297669
]
Vinayakumar B commented on HADOOP-12754:
----------------------------------------
{code} } else {
- String msg = "Couldn't setup connection for "
- + UserGroupInformation.getLoginUser().getUserName() + " to "
- + remoteId;
+ String msg =
+ "Couldn't setup connection for " + ugi + " to " + remoteId;
LOG.warn(msg, ex);
{code}
How about the above change. It will give full details.
> 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
> Priority: Minor
> 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)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
