You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2022/05/13 20:22:00 UTC
[jira] [Commented] (GEODE-10307) Doc changes needed for enable security-manager property
[ https://issues.apache.org/jira/browse/GEODE-10307?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17536868#comment-17536868 ]
ASF subversion and git services commented on GEODE-10307:
---------------------------------------------------------
Commit 0ed779351824eddbdd1b6801268e185b0b321950 in geode's branch refs/heads/develop from Dave Barnes
[ https://gitbox.apache.org/repos/asf?p=geode.git;h=0ed7793518 ]
GEODE-10307: Doc changes needed for enable security-manager property (#7687)
* GEODE-10307: Doc changes needed for enable security-manager property
> Doc changes needed for enable security-manager property
> -------------------------------------------------------
>
> Key: GEODE-10307
> URL: https://issues.apache.org/jira/browse/GEODE-10307
> Project: Geode
> Issue Type: Improvement
> Affects Versions: 1.14.4
> Reporter: Dave Barnes
> Priority: Major
> Labels: pull-request-available
>
> Community member Eric Shu reports:
> Here is the description for enable security properties: (https://geode.apache.org/docs/guide/114/managing/security/enable_security.html)
> security-manager Property
> The authentication callback and the authorization callback that implement the SecurityManager interface are specified with the security-manager property. When this property is defined, authentication and authorization are enabled. The definition of the security-manager property is the fully qualified name of the class that implements the SecurityManager interface. For example:
> security-manager = com.example.security.MySecurityManager
> To ensure that the security-manager property is applied consistently across a cluster, follow these guidelines:
> Specify the security-manager property in a properties file, such as gemfire.properties, not in a cluster configuration file (such as cluster.properties).
> Specify the properties file when you start the first locator for the cluster. The locator will propagate the value to all members (locators and servers) that follow.
> If you must specify the security-manager property for servers (neither necessary nor recommended) make sure its value is exactly identical to that specified for the first locator.
> This is true if the cluster has enabled the cluster configuration service, and new members have set the `use-cluster-configuration=true`.
> Documentation should explain that if cluster configuration is not enabled, you must specify the security-manager property for servers, makng sure its value is exactly identical to that specified for the first locator.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)