geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kirk Lund (JIRA)" <>
Subject [jira] [Updated] (GEODE-3062) security-manager property is ignored when using cluster config
Date Wed, 14 Jun 2017 23:15:00 GMT


Kirk Lund updated GEODE-3062:
    Fix Version/s:     (was: 1.3.0)

> security-manager property is ignored when using cluster config
> --------------------------------------------------------------
>                 Key: GEODE-3062
>                 URL:
>             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

View raw message