See: Description
| Interface | Description | 
|---|---|
| AfterInvocationManager | Reviews the  Objectreturned from a secure object invocation, being able to
 modify theObjector throw anAccessDeniedException. | 
| RunAsManager | Creates a new temporary  Authenticationobject for the current secure object
 invocation only. | 
| Class | Description | 
|---|---|
| AbstractSecurityInterceptor | Abstract class that implements security interception for secure objects. | 
| AfterInvocationProviderManager | Provider-based implementation of  AfterInvocationManager. | 
| InterceptorStatusToken | A return object received by  AbstractSecurityInterceptorsubclasses. | 
| MethodInvocationPrivilegeEvaluator | Allows users to determine whether they have "before invocation" privileges for a given
 method invocation. | 
| RunAsImplAuthenticationProvider | An  AuthenticationProviderimplementation that can authenticate aRunAsUserToken. | 
| RunAsManagerImpl | Basic concrete implementation of a  RunAsManager. | 
| RunAsUserToken | An immutable  Authenticationimplementation
 that supportsRunAsManagerImpl. | 
 A secure object is a term frequently used throughout the security
 system. It does not refer to a business object that is being
 secured, but instead refers to some infrastructure object that can have
 security facilities provided for it by Spring Security.
 For example, one secure object would be MethodInvocation,
 whilst another would be HTTP
 org.springframework.security.web.FilterInvocation. Note these are
 infrastructure objects and their design allows them to represent a large
 variety of actual resources that might need to be secured, such as business
 objects or HTTP request URLs.
 
Each secure object typically has its own interceptor package.
 Each package usually includes a concrete security interceptor (which subclasses
 AbstractSecurityInterceptor) and an
 appropriate SecurityMetadataSource
 for the type of resources the secure object represents.