You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Kirk Lund (JIRA)" <ji...@apache.org> on 2017/06/09 22:07:18 UTC

[jira] [Created] (GEODE-3062) security-manager property is ignored when using cluster config

Kirk Lund created GEODE-3062:
--------------------------------

             Summary: security-manager property is ignored when using cluster config
                 Key: GEODE-3062
                 URL: https://issues.apache.org/jira/browse/GEODE-3062
             Project: Geode
          Issue Type: Bug
          Components: configuration
            Reporter: Kirk Lund


The fix for GEODE-2632 moves the creation of the SecurityService from GemFireCacheImpl to InternalDistributedSystem so that membership can properly use it. Membership needs to use SecurityService for peer-to-peer authentication which occurs before the Cache exists.

Cluster config is requested and applied during initialization of a GemFireCacheImpl instance. So if security-manager property has a value in cluster config, it will be ignored.

Potential short-term fix for this bug is to allow the GemFireCacheImpl object to have its own SecurityService which is created from cluster config properties. 

This only affects servers because secondary locators do not use cluster config (see GEODE-2315).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)