Interface MethodInvocationAuthorizer
- All Known Implementing Classes:
ExampleAnnotationBasedMethodInvocationAuthorizer,JavaBeanAccessorMethodAuthorizer,RegExMethodAuthorizer,RestrictedMethodAuthorizer,UnrestrictedMethodAuthorizer
public interface MethodInvocationAuthorizer
The root interface that should be implemented by method invocation authorizer instances.
The authorizer is responsible for determining whether a
Method is
allowed to be executed on a specific Object instance. Implementations of this
interface should provide a no-arg constructor.
There are mainly four security risks when allowing users to execute arbitrary methods in OQL, which should be addressed by implementations of this interface:
Java Reflection: do anything throughObject.getClass()or similar.Cache Modification: executeCacheoperations (close, get regions, etc.).Region Modification: executeRegionoperations (destroy, invalidate, etc.).Region Entry Modification: execute in-place modifications on the region entries.
Implementations of this interface should be thread-safe: multiple threads might be authorizing several method invocations using the same instance at the same time.
-
Method Summary
Modifier and TypeMethodDescriptionbooleanExecutes the authorization logic to determine whether themethodis allowed to be executed on thetargetobject instance.default voidinitialize(Cache cache, Set<String> parameters)
-
Method Details
-
initialize
-
authorize
Executes the authorization logic to determine whether themethodis allowed to be executed on thetargetobject instance.Implementation Note: the query engine will remember whether the method invocation has been already authorized or not for the current query context, so this method will be called once in the lifetime of a query for every new method seen while traversing the objects. Nevertheless, the implementation should be lighting fast as it will be called by the OQL engine in runtime during the query execution.
-