[
https://issues.apache.org/jira/browse/HADOOP-7070?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12974465#action_12974465
]
Hadoop QA commented on HADOOP-7070:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12466853/hadoop-7070.2.txt
against trunk revision 1051659.
+1 @author. The patch does not contain any @author tags.
+1 tests included. The patch appears to include 3 new or modified tests.
+1 javadoc. The javadoc tool did not generate any warning messages.
+1 javac. The applied patch does not increase the total number of javac
compiler warnings.
+1 findbugs. The patch does not introduce any new Findbugs (version 1.3.9)
warnings.
+1 release audit. The applied patch does not increase the total number of
release audit warnings.
+1 core tests. The patch passed core unit tests.
+1 contrib tests. The patch passed contrib unit tests.
+1 system test framework. The patch passed system test framework compile.
Test results:
https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/147//testReport/
Findbugs warnings:
https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/147//artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Console output:
https://hudson.apache.org/hudson/job/PreCommit-HADOOP-Build/147//console
This message is automatically generated.
> JAAS configuration should delegate unknown application names to pre-existing
> configuration
> ------------------------------------------------------------------------------------------
>
> Key: HADOOP-7070
> URL: https://issues.apache.org/jira/browse/HADOOP-7070
> Project: Hadoop Common
> Issue Type: Bug
> Components: security
> Affects Versions: 0.22.0, 0.23.0
> Reporter: Todd Lipcon
> Assignee: Todd Lipcon
> Priority: Critical
> Attachments: hadoop-7070.2.txt, hadoop-7070.txt, hadoop-7070.txt
>
>
> As reported here: https://issues.cloudera.org/browse/DISTRO-66 it is
> impossible to use secured Hadoop inside an application that relies on other
> JAAS configurations. This is because the static initializer of
> UserGroupInformation replaces the JAAS configuration, but we don't delegate
> unknown applications up to whatever Configuration was installed previously.
> The delegation technique seems to be used by JBoss's XMLLoginConfigImpl for
> example.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
