hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Malaska (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HADOOP-8787) KerberosAuthenticationHandler should include missing property names in configuration
Date Wed, 12 Sep 2012 01:07:07 GMT

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

Ted Malaska updated HADOOP-8787:
--------------------------------

    Attachment: HADOOP-8787-2.patch

This is an implementation of option 1.

I need to review with the hadoop team tomorrow to ask for direction.  I'm not sure which option
is best for this JIRA.

Things included in this patch:
1. Nested exception message that give the user information about which proporties are causing
the problem.
2. It fixed the security null in the case of a prefix bug.
3. It includes a new test for the security null in the case of a prefix bug. 
                
> KerberosAuthenticationHandler should include missing property names in configuration
> ------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8787
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8787
>             Project: Hadoop Common
>          Issue Type: Improvement
>          Components: security
>    Affects Versions: 1.0.3, 3.0.0, 2.0.1-alpha
>            Reporter: Todd Lipcon
>            Assignee: Ted Malaska
>            Priority: Minor
>              Labels: newbie
>         Attachments: HADOOP-8787-0.patch, HADOOP-8787-1.patch, HADOOP-8787-2.patch
>
>
> Currently, if the spnego keytab is missing from the configuration, the user gets an error
like: "javax.servlet.ServletException: Principal not defined in configuration". This should
be augmented to actually show the configuration variable which is missing. Otherwise it is
hard for a user to know what to fix.

--
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

Mime
View raw message