Mailing-List: contact dev-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
MIME-Version: 1.0
In-Reply-To: <CANZq1gDYL_6ekiQeqTpFHy0Zfo69c0FABX8cXppSzHfV0advoQ@mail.gmail.com>
References: <CANZq1gANBm1AYLmSeerFev_pW+SyZVv9JoxPRj5oY726JYK_pw@mail.gmail.com>
 <2EC8B340-A355-4A26-8827-6BEEFC25132C@pivotal.io> <CAFh+7k0LKeLsEMZhthWFQ-A-3twuK99bdgXUjbO+WXMN9VDJ5A@mail.gmail.com>
 <121c32a4-2314-1afb-aebe-bb6dc99bff7c@pivotal.io> <CAFh+7k0QKPSobeg4jgNGgkM6E_uotAtkEyiuRqTx_utuGHve_A@mail.gmail.com>
 <74246de5-cc31-4712-2e15-37983a5aa0f9@pivotal.io> <CANZq1gDYL_6ekiQeqTpFHy0Zfo69c0FABX8cXppSzHfV0advoQ@mail.gmail.com>
From: Dan Smith <dsmith@pivotal.io>
Date: Thu, 17 Aug 2017 13:41:23 -0700
Message-ID: <CAFh+7k0tiGoKK9ryJgvMXQpUDMW3oQ_6-Lqd_oD24C3RfL0vqw@mail.gmail.com>
Subject: Re: [DISCUSS] authorizing function execution
To: dev@geode.apache.org
Content-Type: multipart/alternative; boundary="001a114031e22744a20556f90975"
archived-at: Thu, 17 Aug 2017 20:41:35 -0000

--001a114031e22744a20556f90975
Content-Type: text/plain; charset="UTF-8"

On Thu, Aug 17, 2017 at 12:10 PM, Swapnil Bawaskar <sbawaskar@pivotal.io>
wrote:

> So, it sounds like if we did #1 above: i.e:
> 1) externalize SecurityService so that function author can use it in the
> function.execute code to check authorization.
>
> we could get this to work with lambdas:
> ResultCollector rc = getExecution().execute(context ->
>   context.getCache().getSecurityService().authorizeRead();
>   // perform read
>   context.getResultSender().lastResult(result)
> );
>

I'm a bit confused by this proposal. The current behavior is that a
function requires write. Are you saying that we will change that so that
anyone can execute a function, and then all functions need to call this
method to check for what authorization level they want? I think we should
keep the current behavior of requiring write access by default. Which means
the develop needs a way override the permission level *before* the function
executes.

You could technically make marker interfaces work with lambdas, or if we
provide annotations, users can create their own marker interfaces.

execute((ReadOnlyFunction) context -> ....)

-Dan

--001a114031e22744a20556f90975--