[
https://issues.apache.org/jira/browse/HADOOP-9284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643168#comment-13643168
]
Kihwal Lee commented on HADOOP-9284:
------------------------------------
> This allows a "secure" client to work in a heterogenous security environment.
As I said, if this is the design, the patch is okay. +1.
I am fine with switching between different auth method, but falling back to no
security doesn't seem right, as long as users are allowed to configure security
on. If turning on security in config has no meaning to client, we should at
least update the documentation. But that will be after the completion of the
SASL work.
> Authentication method is wrong if no TGT is present
> ---------------------------------------------------
>
> Key: HADOOP-9284
> URL: https://issues.apache.org/jira/browse/HADOOP-9284
> Project: Hadoop Common
> Issue Type: Sub-task
> Components: security
> Affects Versions: 2.0.0-alpha, 3.0.0
> Reporter: Daryn Sharp
> Assignee: Daryn Sharp
> Attachments: HADOOP-9284.patch, HADOOP-9284.patch
>
>
> If security is enabled, {{UGI.getLoginUser()}} will attempt an os-specific
> login followed by looking for a TGT in the ticket cache. If no TGT is found,
> the UGI's authentication method is still set as KERBEROS instead of SIMPLE.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
