You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2016/09/28 14:51:20 UTC

[jira] [Commented] (GEODE-1659) Prevent misconfiguration of Integrated Security

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

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

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

GEODE-1659: put security properties in the cluster config and applied to all the members in the cluster.

 * break down request and apply cluster configuration into individual steps so that we can apply properties before starting services, and apply cache.xml after services are started
 * added more dunit tests


> 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.
> 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.
> We should also reject members that have disabled security and cluster configuration from joining the cluster.



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