Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id D74D8200CA4 for ; Wed, 24 May 2017 07:37:44 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id D64A6160BD3; Wed, 24 May 2017 05:37:44 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 290FF160BC3 for ; Wed, 24 May 2017 07:37:44 +0200 (CEST) Received: (qmail 34836 invoked by uid 500); 24 May 2017 05:37:43 -0000 Mailing-List: contact dev-help@apex.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@apex.apache.org Delivered-To: mailing list dev@apex.apache.org Received: (qmail 34824 invoked by uid 99); 24 May 2017 05:37:42 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd2-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 May 2017 05:37:42 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd2-us-west.apache.org (ASF Mail Server at spamd2-us-west.apache.org) with ESMTP id 861101A08A9 for ; Wed, 24 May 2017 05:37:42 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd2-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -2.801 X-Spam-Level: X-Spam-Status: No, score=-2.801 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-2.8, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd2-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=datatorrent-com.20150623.gappssmtp.com Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd2-us-west.apache.org [10.40.0.9]) (amavisd-new, port 10024) with ESMTP id ejcMgkDth4EF for ; Wed, 24 May 2017 05:37:41 +0000 (UTC) Received: from mail-pf0-f181.google.com (mail-pf0-f181.google.com [209.85.192.181]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTPS id EFA5C5F23E for ; Wed, 24 May 2017 05:37:40 +0000 (UTC) Received: by mail-pf0-f181.google.com with SMTP id 9so133607020pfj.1 for ; Tue, 23 May 2017 22:37:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=datatorrent-com.20150623.gappssmtp.com; s=20150623; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=4ZGP82sGvrgW39kbU/uAo5lAT+Oz1CiW8UL6OYsrv8Y=; b=YZuPCDjLvNC5L8PAik/P1bzqNbtweNF3BjUhEg5ys6LgarXEaBT209DJUz/Wi8g9lC 2ojihqbK7pl47Uk4k4z0PqW3r0XLLkMBeGBCXFvZZf7bjYSLAuPsSqx/ZOBBSedwp+PQ i8E1f6mOHCR0U9+X85fB8GCgPrh5SDbNCuPGkRx92h0AIlIs1aB0jJBU/e81iIkK7Bgm vwIOk4PsBj3i2l6Zduqysc2hYg/qxMtTHHPeOPlYxy3cn9IjIOXxIghYuggHPvIElE0p uWMyNHxN7Lozx+SuTW93+GYvK1lZ6AauEmIq0zBRXJQ4PjcjiHAJlNKLvAeyptrRo6Bo PZdA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-transfer-encoding:content-language; bh=4ZGP82sGvrgW39kbU/uAo5lAT+Oz1CiW8UL6OYsrv8Y=; b=npv7xgZb8AWrE/BgWo2c5/+RFmfTVsY2Ip4JNYEYpCm1FXp1DFFCG7W2/9g2SQH+xR YWgfJcvIHk+22/dnEg5s2pOCFAa0b+DkiOI9EUgFOQsNgPJfeuJ/UV9CtnEPkClrRG5d YcB7kfxmGp1x0B6sp65BEI+lGtrabDTVI6z5ud9opkxeTXxP7K3CVqPbGNr7TsteV9+n Z3yASWICjjMmErwQaRcBrfVUFufRAEVBxyPmyxj/5/uYIaKQLS271H9kzuXScyC0Psvi pNNeXfY+talP9PJGaakqIdAlfxcDIwTIWZqmlg+tjm6I2Clx/GDBav7IgPgjLXEfPWg1 yTKA== X-Gm-Message-State: AODbwcCklzP3xxPo6T6Vo9NMQYyv+Z63EGqFjpCPSh49K97mDYeT3Eu7 2zERZBdDE98s/AZ8/7s= X-Received: by 10.99.119.7 with SMTP id s7mr35634980pgc.143.1495604254233; Tue, 23 May 2017 22:37:34 -0700 (PDT) Received: from vrozov.local ([2601:646:8482:1283:6892:ea91:ba76:bbdb]) by smtp.googlemail.com with ESMTPSA id r21sm4580375pfg.95.2017.05.23.22.37.33 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 23 May 2017 22:37:33 -0700 (PDT) Subject: Re: [VOTE] impersonation and application path To: dev@apex.apache.org References: <542fa76f-ea2d-e336-f91c-e2bdfa24b3d1@datatorrent.com> From: Vlad Rozov Organization: DataTorrent Message-ID: <0f0c8e9b-b4f5-7037-3639-f198b8f9b59c@datatorrent.com> Date: Tue, 23 May 2017 22:37:32 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.12; rv:52.0) Gecko/20100101 Thunderbird/52.1.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US archived-at: Wed, 24 May 2017 05:37:45 -0000 IMO, it should be different vote. In case APPLICATION_PATH is explicitly specified, it should be used. If it is not specified, there are few options to consider. 1. My suggestion was always default to the impersonated user home directory as a starting point for constructing APPLICATION_PATH 2. Your suggestion is to have another settings that will allow to choose between impersonated and impersonating users. Please propose what will be the default for the new setting ( a) impersonating or b) impersonated). Thank you, Vlad On 5/23/17 22:00, Pramod Immaneni wrote: > I thought it was the mechanism you suggested to specify impersonating > user's directory so I listed it here. If I am mistaken and your option is > not covered, please include it and since it is early in the voting folks > can include it in their voting preference. If not, please provide your > choice. > > Thanks > > On Tue, May 23, 2017 at 9:40 PM, Vlad Rozov wrote: > >> I don't see how option a is applicable here. In case APPLICATION_PATH is >> explicitly specified should not it be used independently of impersonation? >> It can point to any location, not necessarily to home directory of >> impersonating or impersonated user. >> >> Thank you, >> >> Vlad >> >> On 5/23/17 10:34, Pramod Immaneni wrote: >> >>> Based on the discussion on the dev list on this topic, captured here >>> >> 99adc7534431016024f61703b248ce7bfb@%3Cdev.apex.apache.org%3E>, >>> a few different approaches were discussed including the pros and cons. I >>> would like to put the suggested approaches up for a vote. Please go >>> through >>> the thread above if you are unfamiliar with the topic. Here are the >>> options. >>> >>> 1. Let the default remain as the impersonating user >>> a. The user specifies to use impersonated user's directory by >>> setting the APPLICATION_PATH attribute. >>> b. The user specifies the use of impersonated user's resources >>> using >>> a new setting that will internally set the APPLICATION_PATH to the >>> corresponding value and any other resources in the future. >>> >>> 2. Change the default from current behavior to use the impersonated user's >>> resources instead >>> a. and b. similar to 1. but specifying impersonating user's >>> resources instead. >>> >>> My vote is for Option 1, Sub-option b). >>> >>> Thanks >>> >>>