[
https://issues.apache.org/jira/browse/GEODE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16677184#comment-16677184
]
ASF subversion and git services commented on GEODE-5918:
--------------------------------------------------------
Commit d02315d1fc989779da6d364c92beaed947fe728f in geode's branch
refs/heads/develop from [~ivorzhou]
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=d02315d ]
GEODE-5918 Geode function security should be dynamically determined by function
arguments (#2727)
> Geode function security should be dynamically determined by function arguments
> ------------------------------------------------------------------------------
>
> Key: GEODE-5918
> URL: https://issues.apache.org/jira/browse/GEODE-5918
> Project: Geode
> Issue Type: Improvement
> Components: functions, security
> Reporter: ivorzhou
> Priority: Critical
> Labels: pull-request-available
> Time Spent: 1h 20m
> Remaining Estimate: 0h
>
> Now in Function interface there is a method
> default Collection<ResourcePermission> getRequiredPermissions(String
> regionName) {
> return Collections.singletonList(ResourcePermissions.DATA_WRITE);
> }
>
> Which only support statically security determination in design
> time(regionName is not enough).
> In some situation,we require determining security on function arguments.
>
> I think add a method in this interface like
> default Collection<ResourcePermission> getRequiredPermissions(String
> regionName,Object args) {
> return getRequiredPermissions(regionName);
> }
>
> and in server side command,call the new method with regionName and arguments
> together.
>
>
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
