Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id A7FD82009C6 for ; Tue, 17 May 2016 02:39:17 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id A688E160A21; Tue, 17 May 2016 00:39:17 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id F00DB160A16 for ; Tue, 17 May 2016 02:39:16 +0200 (CEST) Received: (qmail 25195 invoked by uid 500); 17 May 2016 00:39:16 -0000 Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.incubator.apache.org Delivered-To: mailing list issues@geode.incubator.apache.org Received: (qmail 25185 invoked by uid 99); 17 May 2016 00:39:16 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 May 2016 00:39:16 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id CAC2D1803EA for ; Tue, 17 May 2016 00:39:15 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -4.021 X-Spam-Level: X-Spam-Status: No, score=-4.021 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id 4rLRN2qIE5Wa for ; Tue, 17 May 2016 00:39:15 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with SMTP id 5DC3D5FE65 for ; Tue, 17 May 2016 00:39:14 +0000 (UTC) Received: (qmail 24400 invoked by uid 99); 17 May 2016 00:39:13 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 May 2016 00:39:13 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id 5F9772C1F77 for ; Tue, 17 May 2016 00:39:13 +0000 (UTC) Date: Tue, 17 May 2016 00:39:13 +0000 (UTC) From: "ASF subversion and git services (JIRA)" To: issues@geode.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (GEODE-17) Provide Integrated Security MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Tue, 17 May 2016 00:39:17 -0000 [ https://issues.apache.org/jira/browse/GEODE-17?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15285735#comment-15285735 ] ASF subversion and git services commented on GEODE-17: ------------------------------------------------------ Commit 428bb51d90a74a850fd0a8cf6a46f26eef2a09ce in incubator-geode's branch refs/heads/feature/GEODE-1209 from [~jinmeiliao] [ https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;h=428bb51 ] GEODE-17: pulse not started with gemfire security enabled > 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)