Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.incubator.apache.org
Date: Tue, 3 May 2016 17:15:13 +0000 (UTC)
From: "ASF subversion and git services (JIRA)" <jira@apache.org>
To: issues@geode.incubator.apache.org
Message-ID: <JIRA.12828330.1431085656000.99856.1462295713120@Atlassian.JIRA>
In-Reply-To: <JIRA.12828330.1431085656000@Atlassian.JIRA>
References: <JIRA.12828330.1431085656000@Atlassian.JIRA> <JIRA.12828330.1431085656341@arcas>
Subject: [jira] [Commented] (GEODE-17) Provide Integrated Security
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 03 May 2016 17:15:16 -0000


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

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

Commit b8fc3c706ef672c48a04f7c6ec4bf593414c6494 in incubator-geode's branch refs/heads/develop from [~jinmeiliao]
[ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=b8fc3c7 ]

GEODE-17 - use null instead of "NULL" for regionName

* create an example JSONAuthorization that initialize with a default security.json file.


> 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)