|
@@ -1,26 +0,0 @@
|
|
-<html>
|
|
|
|
-<body>
|
|
|
|
-Actually enforces the security and ties the whole security system together.
|
|
|
|
-<p>
|
|
|
|
-A <i>secure object</i> is a term frequently used throughout the security
|
|
|
|
-system. It does <b>not</b> 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 <code>MethodInvocation</code>,
|
|
|
|
-whilst another would be HTTP
|
|
|
|
-{@link 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.
|
|
|
|
-</p>
|
|
|
|
-
|
|
|
|
-<p>Each secure object typically has its
|
|
|
|
-own interceptor package.
|
|
|
|
-Each package usually includes a concrete security interceptor (which
|
|
|
|
-subclasses {@link org.springframework.security.access.intercept.AbstractSecurityInterceptor},
|
|
|
|
-an appropriate {@link org.springframework.security.access.SecurityMetadataSource}
|
|
|
|
-for the type of resources the secure object represents, and a property editor
|
|
|
|
-to populate the <code>SecurityMetadataSource</code>.
|
|
|
|
-
|
|
|
|
-</body>
|
|
|
|
-</html>
|
|
|