Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Tue, 27 Sep 2011 16:41:45 +0000 (UTC)
From: "Thomas Graves (Commented) (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <671469811.63.1317141705522.JavaMail.tomcat@hel.zones.apache.org>
In-Reply-To: 
 <1857764010.22801.1315934349156.JavaMail.tomcat@hel.zones.apache.org>
Subject: [jira] [Commented] (MAPREDUCE-2999) hadoop.http.filter.initializers
 not working properly on yarn UI
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MAPREDUCE-2999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13115695#comment-13115695 ] 

Thomas Graves commented on MAPREDUCE-2999:
------------------------------------------

Manual testing done:

Test with and without an auth filter (config settinghadoop.http.filter.initializers).  When filter setting is set verified that the load of each page properly went through the filter specified. When going through the filter the page properly showed the current User in the upper right hand corner.  Without the filter it shows the default hadoop user of "dr.who".  Modified my auth filter to be able to choose which pages to actually authenticate and which not to.  When it didn't authenticate pages verified that anyone could go there and the upper right corner was empty (didn't show the "Logged in as:").

Tested that all the yarn web pages and links from yarn web pages to other pages worked.  For instance RM page has link to node manager, links from app to job history and to app master.  Verified the links from app master back to RM work,  etc... and that when the filter is there they properly go through the filter and ask for authentication.

Verify that each yarn web app allows the user to get there from:
  - host:port/         ->  This redirects you to host:port/yarn so that the filter can differentiate and chose to authenticate or not
  - host:port/yarn     -> goes to default page specified by webapp
  - host:port/yarn/*   -> goes to page specified by webapp

Verify that all of the default applications registered in HttpServer still work.  (note that HADOOP-7662 is needed for the /logs to work).
  - /logs
  - /static
  - /stacks
  - /logLevel
  - /metrics
  - /jmx
  - /conf

                
> hadoop.http.filter.initializers not working properly on yarn UI
> ---------------------------------------------------------------
>
>                 Key: MAPREDUCE-2999
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-2999
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: mrv2
>    Affects Versions: 0.23.0
>            Reporter: Thomas Graves
>            Assignee: Thomas Graves
>            Priority: Critical
>             Fix For: 0.23.0
>
>         Attachments: MAPREDUCE-2999.patch, MAPREDUCE-2999.patch, MAPREDUCE-2999.patch, MAPREDUCE-2999.patch, MAPREDUCE-2999.patch, MAPREDUCE-2999.patch
>
>
> Currently httpserver only has *.html", "*.jsp as user facing urls when you add a filter. For the new web framework in yarn, the pages no longer have the *.html or *.jsp and thus they are not properly being filtered.

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