Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 4D2B0108AD for ; Tue, 10 Dec 2013 20:07:54 +0000 (UTC) Received: (qmail 20555 invoked by uid 500); 10 Dec 2013 20:07:49 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 20379 invoked by uid 500); 10 Dec 2013 20:07:48 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 20372 invoked by uid 99); 10 Dec 2013 20:07:48 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Dec 2013 20:07:48 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of thomas.weise@gmail.com designates 209.85.214.180 as permitted sender) Received: from [209.85.214.180] (HELO mail-ob0-f180.google.com) (209.85.214.180) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 10 Dec 2013 20:07:41 +0000 Received: by mail-ob0-f180.google.com with SMTP id wo20so5789642obc.25 for ; Tue, 10 Dec 2013 12:07:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=9YACCNa7QSUs83MEVnSkApo4BfnRezN5q/rLKHWXmm8=; b=Eb84gCwIxDB7q5zupQQ99MnnPe8Rify20ui5f7Oh0sBhjMCct1nIZ7uCefFwgVaEm0 Liw5+ybrQDj/NE9I7aRGafb10dNb+lq2zlIWN9TUpegbqiNVXfGh8u4EnnJH/J73hPU4 fuzwl5j1RtR2ZoEcrkJVhgSTIUFTZyuWLR2gUjFx17zDcMm2bd/sdxdLkARWrVcHnytB vofpSl89oiPZv4dE5CWX5pWb7aNBFnWp4AOGpCP/vbLP45YNMsSCXnNNEQUiruareKUh zVUrQgTMlUqIZTwWsem9hkJNFllFNxsRK+dIJ38A3b+EZta6Y6n0Zon3o4c0L8TjlgAV DEuQ== MIME-Version: 1.0 X-Received: by 10.60.60.71 with SMTP id f7mr1652746oer.82.1386706041054; Tue, 10 Dec 2013 12:07:21 -0800 (PST) Received: by 10.182.17.34 with HTTP; Tue, 10 Dec 2013 12:07:21 -0800 (PST) Date: Tue, 10 Dec 2013 12:07:21 -0800 Message-ID: Subject: AM web app security in 2.2 From: Thomas Weise To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=089e0149ca10fc2e6704ed33a857 X-Virus-Checked: Checked by ClamAV on apache.org --089e0149ca10fc2e6704ed33a857 Content-Type: text/plain; charset=ISO-8859-1 What is the recommended way to secure the AM app master web app (if any) in 2.x? The client can obtain the tracking URL from the app report using appReport.getOriginalTrackingUrl() and bypass the RM proxy. In case of POST request, which is not currently supported by the proxy, that is the only option. How does this work with the MR app master web application? Thanks! --089e0149ca10fc2e6704ed33a857 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
What is the recommended way to secure the AM app master we= b app (if any) in 2.x? The client can obtain the tracking URL from the app = report using appReport.getOriginalTrackingUrl() and bypass the RM proxy. In case of POST r= equest, which is not currently supported by the proxy, that is the only opt= ion.=A0

How does this work with the MR app master web application?

Thanks!


--089e0149ca10fc2e6704ed33a857--