[
https://issues.apache.org/jira/browse/GEODE-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16049771#comment-16049771
]
ASF subversion and git services commented on GEODE-3062:
--------------------------------------------------------
Commit a79d2cc1621bd8c36531519df5e1edbb0faabf96 in geode's branch
refs/heads/develop from [[email protected]]
[ https://git-wip-us.apache.org/repos/asf?p=geode.git;h=a79d2cc ]
Revert "GEODE-3062: create new SecurityService after receiving cluster config"
This reverts commit cecad6c37d59369a29237f7d940f297804633aa1.
> 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
> Fix For: 1.3.0
>
>
> 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.4.14#64029)
