[
https://issues.apache.org/jira/browse/HADOOP-8787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13453575#comment-13453575
]
Ted Malaska commented on HADOOP-8787:
-------------------------------------
Hmm, this is an interesting JIRA. The problem is really simple, but being my
first Hadoop JIRA I'm not sure the right course of action.
I have the following options:
1. Throw nested exceptions: The outer exception will have the prefix
"dfs.web.authentication.kerberos.principal" and the inner exception will have
the root config "kerberos.principal". I know if I was a user I wouldn't like
this option.
2. Instead of striping off the prefixes I could pass the prefix into the init
method of the AuthenicationHandler. That way I would have the full string to
build the original exception message. However I assume someone found value in
striping off those prefixes.
3. I could pass in the prefix to the handler so the solo reason of constructing
the exception message. This option doesn't smell right.
4. I could read the exception message in the AuthenticationFilter and add the
prefix, but that seems like a hack.
So I think I'm going to go with option 2. If anyone can think of a better
option place let me know.
> 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
>
>
> 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
