Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
Description
Add concurrent distributed tests to make sure the following conditions are met once there is an API implemented to change the MethodInvocationAuthorizer in runtime:
- Once a query execution starts, the MethodInvocationAuthorizer used can not be changed for that particular query.
- Once the MethodInvocationAuthorizer is changed through the API or the alter-query-service command, all queries executed afterwards use the newly configured MethodInvocationAuthorizer.
- Any continuous query already running should pick up the new MethodInvocationAuthorizer the next time the query is internally executed to detect whether a cache event matches or not. If the continuous query has methods that are not authorized by the newly configured MethodInvocationAuthorizer, then any matching events from that moment on should invoke CqListener.onError instead of CqListener.onEvent.
- Any configured index should pick up the newly configured MethodInvocationAuthorizer the next time an entry is added or removed from the index (regular region operations), and the index should be marked as invalid if it uses method invocations not authorized by the newly configured MethodInvocationAuthorizer.
Attachments
Issue Links
- is a child of
-
GEODE-6983 Epic for OQL Method Invocation Security
- Closed
- is blocked by
-
GEODE-7486 IndexManager is not consistent
- Closed
-
GEODE-6990 Implement Configuration Options for Method Authorizer
- Closed
-
GEODE-6991 Create AlterQueryService GFSH Command
- Closed
-
GEODE-6995 Use the Correct MethodInvocationAuthorizer
- Closed
-
GEODE-7283 OQL Method Authorizer in Query Execution Context
- Closed
-
GEODE-7313 Refactor QuerySecurityBase
- Closed
-
GEODE-7487 Running CQs should always use the latest installed Method Invocation Authorizer
- Closed
-
GEODE-7497 QueryConfigurationService: Execute CQ Sanity Check Before Changing the MethodInvocationAuthorizer
- Closed
- links to