geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <>
Subject [jira] [Commented] (GEODE-1648) Provide ability to disable security for some components
Date Tue, 02 Aug 2016 18:43:20 GMT


ASF GitHub Bot commented on GEODE-1648:

Github user jinmeiliao commented on a diff in the pull request:
    --- Diff: geode-core/src/main/java/com/gemstone/gemfire/management/internal/
    @@ -509,8 +510,7 @@ private void registerAccessControlMBean() {
       private boolean isIntegratedSecurity() {
    --- End diff --
    We can get rid of this method. I believe this is called to check if we need to enabled
pulse security in the same file as well. Yeah, what about pulse security? Do we need to add
another enum or just say if jmx is enabled. pulse should be enabled as well?

> Provide ability to disable security for some components
> -------------------------------------------------------
>                 Key: GEODE-1648
>                 URL:
>             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:
> 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

View raw message