You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ivorzhou (JIRA)" <ji...@apache.org> on 2018/10/24 03:05:00 UTC
[jira] [Updated] (GEODE-5918) Geode function security should be
dynamically determined by function arguments
[ https://issues.apache.org/jira/browse/GEODE-5918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ivorzhou updated GEODE-5918:
----------------------------
Priority: Critical (was: Major)
> 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
>
> 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)