Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Sat, 11 Feb 2012 00:10:59 +0000 (UTC)
From: "Alejandro Abdelnur (Commented) (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: 
 <289447573.26759.1328919059712.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1631770692.17849.1328756884627.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (HADOOP-8043) KerberosAuthenticationFilter and
 friends have some problems
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HADOOP-8043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13205901#comment-13205901 ] 

Alejandro Abdelnur commented on HADOOP-8043:
--------------------------------------------

Regarding 'That assumes ..', not really it assumes the user knows the hostname it must use. Otherwise, on the server side we would have to have/load a TGT for every possible hostname the server is known by (refer to my second paragraph in my prev comment)

Regarding 'if there is another way...', the same way JT/NN/DN/TT do for initializing UGI with the keytab.
                
> KerberosAuthenticationFilter and friends have some problems
> -----------------------------------------------------------
>
>                 Key: HADOOP-8043
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8043
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: security
>    Affects Versions: 1.0.0
>            Reporter: Allen Wittenauer
>            Priority: Critical
>         Attachments: HADOOP-8043-branch-1.0.txt
>
>
> KerberosAuthenticationFilter and friends have three killer usability issues and bugs:
> 1. Documentation is misleading/wrong.
> 2. Shared secret stored in a world readable file.
> 3. Lacks support for _HOST macro

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira