geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nilkanth Patel (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-17) Provide Integrated Security
Date Wed, 12 Aug 2015 17:48:46 GMT

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

Nilkanth Patel commented on GEODE-17:
-------------------------------------

is requirement for this feature changed..? I think, Initially it was designed with the consideration
that we should not change existing security C/S interfaces, rather utilizing  the same for
other non-secure channels. Is changes to public security interfaces are now in scope?

> Provide Integrated Security
> ---------------------------
>
>                 Key: GEODE-17
>                 URL: https://issues.apache.org/jira/browse/GEODE-17
>             Project: Geode
>          Issue Type: New Feature
>          Components: client/server, core, management & tools
>            Reporter: Tushar Khairnar
>            Assignee: Tushar Khairnar
>              Labels: security
>
> Integrated Security: Purpose of integrated security feature is to provide uniform authentication
and authorization capabilities for all Geode clients. Geode distributed systems has different
clients, some perform cache/region operations, some perform management operations. In order
to authenticate and authorize these actions we need single consistent framework or interface.
Such interface should allow configuration of access levels from single place and/or repository.

> The key requirements being met here are
>  - Authentication of all clients from single plugin
>  - Authorization of cache/data operations (through cache-client and REST) and managements
(GFSH/JMX) operations from single plugin
>  - Extend existing Client-Server security framework



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

Mime
View raw message