You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Alexander Murmann (JIRA)" <ji...@apache.org> on 2018/11/08 21:16:00 UTC
[jira] [Resolved] (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 ]
Alexander Murmann resolved GEODE-5918.
--------------------------------------
Resolution: Fixed
[~ivorzhou] Your commit is merged and made it into the 1.8.0 release branch. I am closing this, assuming this will be delivering the desired functionality in 1.8.0. Please let me know if that is not the right way forward.
Thanks!
> 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
> Fix For: 1.8.0
>
> 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)