geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-17) Provide Integrated Security
Date Fri, 11 Mar 2016 22:24:54 GMT

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

ASF subversion and git services commented on GEODE-17:
------------------------------------------------------

Commit 44b248cbe727e88fd078fedbf806a7a83f616fea in incubator-geode's branch refs/heads/feature/GEODE-17-2
from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=44b248c ]

GEODE-17: more cleanup

* break the cirucular dependency in MBeanServerWrapper and ManagementInterceptor
* Now custom authenticator and authorizer can be set independant of each other
* re-arrange the tests
* add test to test local JMX calls to make sure they don't go through the MBeanServerWrapper

Merge branch 'feature/GEODE-17-2' of https://git-wip-us.apache.org/repos/asf/incubator-geode
into feature/GEODE-17-2


> Provide Integrated Security
> ---------------------------
>
>                 Key: GEODE-17
>                 URL: https://issues.apache.org/jira/browse/GEODE-17
>             Project: Geode
>          Issue Type: New Feature
>          Components: client/server, docs, security
>            Reporter: Tushar Khairnar
>            Assignee: Jens Deppe
>              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