You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/07/20 18:19:00 UTC
[jira] [Commented] (GEODE-3108) secure ability to create lucene
indexes
[ https://issues.apache.org/jira/browse/GEODE-3108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16095143#comment-16095143 ]
ASF subversion and git services commented on GEODE-3108:
--------------------------------------------------------
Commit b71f3a636175a26974fae88a5090ed4d94ccce73 in geode's branch refs/heads/develop from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=b71f3a6 ]
GEODE-3108: update lucene security permission to use "LUCENE" target
* have lucene module define it's own target for plugability
* added string based target support for SecurityService
> secure ability to create lucene indexes
> ---------------------------------------
>
> Key: GEODE-3108
> URL: https://issues.apache.org/jira/browse/GEODE-3108
> Project: Geode
> Issue Type: Sub-task
> Components: docs, security
> Reporter: Swapnil Bawaskar
> Assignee: Kenneth Howe
>
> Treat queries as a CLUSTER resource so that administrators can control ability to manage indices (both OQL and Lucene), and manage Continuous queries.
> Only a user with CLUSTER:MANAGE:LUCENE should be able to run the following gfsh commands:
> {noformat}
> create lucene index
> destroy lucene index
> {noformat}
> A user with CLUSTER:READ:LUCENE should be able to run the following commands:
> {noformat}
> describe lucene index
> list lucene indexes
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)