You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Barbara Pruijn (JIRA)" <ji...@apache.org> on 2018/03/01 21:17:00 UTC
[jira] [Resolved] (GEODE-2822) gfsh commds 'list index' and
'describe index' should not require CLUSTER:READ permission
[ https://issues.apache.org/jira/browse/GEODE-2822?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Barbara Pruijn resolved GEODE-2822.
-----------------------------------
Resolution: Invalid
This is the new way of setting permissions:
https://cwiki.apache.org/confluence/display/GEODE/Finer+grained+security
> gfsh commds 'list index' and 'describe index' should not require CLUSTER:READ permission
> ----------------------------------------------------------------------------------------
>
> Key: GEODE-2822
> URL: https://issues.apache.org/jira/browse/GEODE-2822
> Project: Geode
> Issue Type: Bug
> Components: docs, gfsh, security
> Reporter: Diane Hardman
> Priority: Major
>
> To create either an OQL index or a Lucene index requires DATA:MANAGE permission. Once I've created an index, I should be able to get a list of the indexes and/or a description of the indexes with the same permission.
> Instead, today, listing or describing indexes requires CLUSTER:READ permission. This would require every developer with DATA:MANAGE permission to also have CLUSTER:READ permission to examine what they were able to create. This doesn't make sense to me.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)