[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=17536874#comment-17536874 ] ASF subversion and git services commented on GEODE-10307: - Commit d8c401699b346d3e3922da993a5d68ef11138836 in geode's branch refs/heads/support/1.12 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=d8c401699b ] 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)
[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=17536872#comment-17536872 ] ASF subversion and git services commented on GEODE-10307: - Commit 08fe5c543c1ebf6c9b09776a1b1e16afac7acb41 in geode's branch refs/heads/support/1.15 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=08fe5c543c ] 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)
[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=17536871#comment-17536871 ] ASF subversion and git services commented on GEODE-10307: - Commit f0664f11972ea30c4e4e9462118cba7b10d5e6ff in geode's branch refs/heads/support/1.14 from Dave Barnes [ https://gitbox.apache.org/repos/asf?p=geode.git;h=f0664f1197 ] 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)
[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=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)
