Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Message-ID: <32481491.225821292887142163.JavaMail.jira@thor>
Date: Mon, 20 Dec 2010 18:19:02 -0500 (EST)
From: "Todd Lipcon (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Subject: [jira] Created: (HADOOP-7070) JAAS configuration should delegate
 unknown application names to pre-existing configuration
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

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


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.