[
https://issues.apache.org/jira/browse/GEODE-1571?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375400#comment-15375400
]
ASF subversion and git services commented on GEODE-1571:
--------------------------------------------------------
Commit 29b4870286ee28aac8db1e05a9012eb617354fd7 in incubator-geode's branch
refs/heads/develop from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=29b4870 ]
GEODE-1571: use constructor instead of static method to create security-manager
and post-processor
* use security-post-processor to specify the new PostProcessor
* use constructor instead of static method to create security-manager and
post-processor
* fix tests
* This closes #198
> Client security should be able to use Resource:Operation permissions
> --------------------------------------------------------------------
>
> Key: GEODE-1571
> URL: https://issues.apache.org/jira/browse/GEODE-1571
> Project: Geode
> Issue Type: Sub-task
> Components: security
> Reporter: Swapnil Bawaskar
>
> While providing role based access control for JMX and CLI, noun-verby
> permission of the form of RESOURCE:OPERATION[:REGION] have been introduced.
> Please refer to the wiki for more details:
> https://cwiki.apache.org/confluence/display/GEODE/How+to+secure+JMX+and+GFSH
> We now need to provide a new interface so that client-server security can
> also use these noun-verby permissions.
> To make Geode security "integrated", users will only have to provide an
> implementation of this new interface and it will work for JMX, gfsh and
> client-server.
> {{com.gemstone.gemfire.security.AccessControl}} should be deprecated once we
> have this new interface.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
