Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Fri, 17 Feb 2012 22:46:58 +0000 (UTC)
From: "Jonathan Eagles (Updated) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: 
 <1571918100.52439.1329518818294.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1747566673.52368.1329517017195.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Updated] (MAPREDUCE-3878) byauth bypass paths doesn't work
 on jobhistory job page
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Jonathan Eagles updated MAPREDUCE-3878:
---------------------------------------

    Attachment: MAPREDUCE-3878.patch
    
> byauth bypass paths doesn't work on jobhistory job page
> -------------------------------------------------------
>
>                 Key: MAPREDUCE-3878
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-3878
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.1
>            Reporter: Jonathan Eagles
>            Assignee: Jonathan Eagles
>            Priority: Critical
>         Attachments: MAPREDUCE-3878.patch
>
>
> If jobhistory/job.* is included in the byauth.bypass.paths. URL will always show Null user. This differs from 0.20 where this setting disables security on this page. Bypassing the filter essentially passes a null user to AppController where an exception is thrown. If a null user is detected, we should assume security is disabled on this page.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira