Github user asfgit closed the pull request at:
https://github.com/apache/geode/pull/660
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabl
Github user karensmolermiller commented on a diff in the pull request:
https://github.com/apache/geode/pull/660#discussion_r129917470
--- Diff:
geode-docs/managing/security/implementing_authorization.html.md.erb ---
@@ -56,13 +56,23 @@ which classifies whether the operation as
Github user jinmeiliao commented on a diff in the pull request:
https://github.com/apache/geode/pull/660#discussion_r129910320
--- Diff:
geode-docs/managing/security/implementing_authorization.html.md.erb ---
@@ -56,13 +56,23 @@ which classifies whether the operation as
The op
Github user jinmeiliao commented on a diff in the pull request:
https://github.com/apache/geode/pull/660#discussion_r129908926
--- Diff:
geode-docs/managing/security/implementing_authorization.html.md.erb ---
@@ -56,13 +56,23 @@ which classifies whether the operation as
The op
GitHub user karensmolermiller opened a pull request:
https://github.com/apache/geode/pull/660
GEODE-2924 Revise authorization permissions
For finer-grained security, identify new targets for CLUSTER
operations (DISK, GATEWAY, QUERY, JAR). And, revise 4
operations listed in th