geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Swapnil Bawaskar (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-1713) CQ client commands have inconsistent security support
Date Thu, 28 Jul 2016 21:40:20 GMT

    [ https://issues.apache.org/jira/browse/GEODE-1713?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15398261#comment-15398261
] 

Swapnil Bawaskar commented on GEODE-1713:
-----------------------------------------

We definitely should add security to ExecuteCQ61, since that is the command used by the latest
clients.
Since we will support old clients working with the new Integrated security callbacks on the
server, we should add security to ExecuteCQ.

Since there was no security for GetCQStats and MonitorCQ, I think we could have omitted them
from new IntegratedSecurity, but since they have been implemented already, I would suggest
leaving them in.

> CQ client commands have inconsistent security support
> -----------------------------------------------------
>
>                 Key: GEODE-1713
>                 URL: https://issues.apache.org/jira/browse/GEODE-1713
>             Project: Geode
>          Issue Type: Bug
>          Components: security
>            Reporter: Grace Meilen
>            Assignee: Kirk Lund
>
> The following CQ client commands appear to be using old security but not new Integrated
Security:
> * ExecuteCQ
> * ExecuteCQ61
> The following appear to be using new Integrated Security but not old security (these
may not need any security):
> * GetCQStats
> * MonitorCQ



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message