This is an automated email from the ASF dual-hosted git repository.
dbarnes pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/geode.git
The following commit(s) were added to refs/heads/develop by this push:
new b253ab9 GEODE-5461 - Docs: Specifying the security-manager property
(#2171)
b253ab9 is described below
commit b253ab9aaf5ecf82c656cd03c348e1eb3ce9a5aa
Author: Dave Barnes <[email protected]>
AuthorDate: Fri Jul 20 14:36:48 2018 -0700
GEODE-5461 - Docs: Specifying the security-manager property (#2171)
* GEODE-5461 - Docs: Specifying the security-manager property
---
geode-docs/managing/security/enable_security.html.md.erb | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/geode-docs/managing/security/enable_security.html.md.erb
b/geode-docs/managing/security/enable_security.html.md.erb
index 1263504..a86428f 100644
--- a/geode-docs/managing/security/enable_security.html.md.erb
+++ b/geode-docs/managing/security/enable_security.html.md.erb
@@ -34,6 +34,12 @@ 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.
+
All components of the system invoke the same callbacks.
Here are descriptions of the components and the connections that they
make with the system.
