Mailing-List: contact issues-help@geode.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.incubator.apache.org
Date: Mon, 19 Sep 2016 16:44:20 +0000 (UTC)
From: "Swapnil Bawaskar (JIRA)" <jira@apache.org>
To: issues@geode.incubator.apache.org
Message-ID: <JIRA.12988829.1468353365000.606869.1474303460758@Atlassian.JIRA>
In-Reply-To: <JIRA.12988829.1468353365000@Atlassian.JIRA>
References: <JIRA.12988829.1468353365000@Atlassian.JIRA> <JIRA.12988829.1468353365775@arcas>
Subject: [jira] [Updated] (GEODE-1659) Prevent misconfiguration of
 Integrated Security
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Mon, 19 Sep 2016 16:44:24 -0000


     [ https://issues.apache.org/jira/browse/GEODE-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Swapnil Bawaskar updated GEODE-1659:
------------------------------------
    Summary: Prevent misconfiguration of Integrated Security  (was: Help prevent misconfiguration of Integrated Security)

> Prevent misconfiguration of Integrated Security
> -----------------------------------------------
>
>                 Key: GEODE-1659
>                 URL: https://issues.apache.org/jira/browse/GEODE-1659
>             Project: Geode
>          Issue Type: Sub-task
>          Components: security
>            Reporter: Swapnil Bawaskar
>
> All the locators and all the servers need to be configured with {{security-manager}} geode property to enable integrated security. If a user misses specifying this property even on one member, we end up compromising the entire cluster.
> To prevent this, we should log a warning message in the logs and in gfsh console when a member is started without security when existing members are configured with security.
> In the long term we need to make security-manager part of cluster config properties, so that any new member joining the system will be able to inherit this property.


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