[
https://issues.apache.org/jira/browse/GEODE-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045131#comment-16045131
]
ASF subversion and git services commented on GEODE-3062:
--------------------------------------------------------
Commit d15934fcb41223f1d665d8b2885c6487bd55813e in geode's branch
refs/heads/feature/GEODE-3062 from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=d15934f ]
Add test that fails due to GEODE-3062
> 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
> Assignee: 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)
