You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Swapnil Bawaskar (JIRA)" <ji...@apache.org> on 2016/07/09 13:40:10 UTC
[jira] [Commented] (GEODE-1647) Enable use of SecurityManager for
peer authentication
[ https://issues.apache.org/jira/browse/GEODE-1647?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15369089#comment-15369089 ]
Swapnil Bawaskar commented on GEODE-1647:
-----------------------------------------
Since a Geode distributed system is typically deployed behind a firewall, peer-to-peer authentication is not required as frequently as client-server authentication. Hence there should be a way to disable peer-to-peer authentication when {{SecurityManager}} is used.
I propose that we add a new geode property {{enable-peer-to-peer-authentication}} which is true by default, but can be set to false when peer-to-peer authentication is not required.
> Enable use of SecurityManager for peer authentication
> -----------------------------------------------------
>
> Key: GEODE-1647
> URL: https://issues.apache.org/jira/browse/GEODE-1647
> Project: Geode
> Issue Type: Sub-task
> Components: security
> Reporter: Kirk Lund
> Assignee: Grace Meilen
>
> Since the clients and JMX both support SecurityManager for authentication, the peer-to-peer authentication should also be able to use SecurityManager so that the users could truly have one callback for all authentication.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)