geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirk Lund (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (GEODE-3062) security-manager property is ignored when using cluster config
Date Thu, 22 Jun 2017 19:44:00 GMT

     [ https://issues.apache.org/jira/browse/GEODE-3062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kirk Lund resolved GEODE-3062.
------------------------------
       Resolution: Fixed
    Fix Version/s: 1.3.0

> 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)

Mime
View raw message