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

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

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

GEODE-1648: commits related to security-enabled-components.


> Provide ability to disable security for some components
> -------------------------------------------------------
>
>                 Key: GEODE-1648
>                 URL: https://issues.apache.org/jira/browse/GEODE-1648
>             Project: Geode
>          Issue Type: Sub-task
>          Components: security
>            Reporter: Swapnil Bawaskar
>            Assignee: Jinmei Liao
>             Fix For: 1.0.0-incubating
>
>
> When the new {{SecurityManager}} interface is used, it will enable 
> authentication and authorization for client-server, jmx, peer-to-peer and 
> WAN. Not all users will want authentication and authorization for all these 
> components as explained in this comment: 
> https://issues.apache.org/jira/browse/GEODE-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369089#comment-15369089
> We should add new geode properties:
> {noformat}
> enable-peer-to-peer-authentication
> enable-client-server-security
> enable-msnsgement-security
> {noformat}
> Update:
> Rather than introducing three new properties, we should add a single new 
> property: {{security-enabled-components}} which will have a default value of 
> {{all}} and can be configured with the same list of components being worked 
> on in GEODE-420. 



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

Reply via email to