[
https://issues.apache.org/jira/browse/GEODE-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15404552#comment-15404552
]
ASF GitHub Bot commented on GEODE-1648:
---------------------------------------
Github user jinmeiliao commented on a diff in the pull request:
https://github.com/apache/incubator-geode/pull/224#discussion_r73211230
--- Diff:
geode-core/src/main/java/com/gemstone/gemfire/internal/security/GeodeSecurityUtil.java
---
@@ -471,16 +499,27 @@ public static PostProcessor getPostProcessor() {
return postProcessor;
}
- public static boolean isClientSecurityRequired() {
- return isClientAuthenticator || isIntegratedSecurity;
+ public static boolean isIntegratedSecurity(){
--- End diff --
We can get rid of this public method now. I believe now all the other
components are just using component specific security enabled function.
> 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
>
> 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}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
