hadoop-common-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Owen O'Malley (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-7070) JAAS configuration should delegate unknown application names to pre-existing configuration
Date Thu, 23 Dec 2010 00:10:01 GMT

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

Owen O'Malley commented on HADOOP-7070:
---------------------------------------

How about a simple check to see if it is already a Hadoop configuration and skip the install
in that case?

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


Mime
View raw message