[GEODE-3062] security-manager property is ignored when using cluster config

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.3.0
• Component/s: configuration
• Assignee: Kirk Lund
• Reporter: Kirk Lund
• Created: 09/Jun/17 22:06
• Updated: 20/Apr/18 19:53
• Resolved: 22/Jun/17 19:43

Description

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

Issue Links

• blocks: GEODE-2632 Integrated Security performance improvements