Add AuthorizationManager for protect-pointcut
Closes gh-11323
This commit is contained in:
@@ -202,8 +202,8 @@ msmds.attlist &= id?
|
||||
msmds.attlist &= use-expressions?
|
||||
|
||||
method-security =
|
||||
## Provides method security for all beans registered in the Spring application context. Specifically, beans will be scanned for matches with Spring Security annotations. Where there is a match, the beans will automatically be proxied and security authorization applied to the methods accordingly. Interceptors are invoked in the order specified in AuthorizationInterceptorsOrder. Use can create your own interceptors using Spring AOP.
|
||||
element method-security {method-security.attlist, expression-handler?}
|
||||
## Provides method security for all beans registered in the Spring application context. Specifically, beans will be scanned for matches with Spring Security annotations. Where there is a match, the beans will automatically be proxied and security authorization applied to the methods accordingly. Interceptors are invoked in the order specified in AuthorizationInterceptorsOrder. Use can create your own interceptors using Spring AOP. Also, annotation-based interception can be overridden by expressions listed in <protect-pointcut> elements.
|
||||
element method-security {method-security.attlist, expression-handler?, protect-pointcut*}
|
||||
method-security.attlist &=
|
||||
## Specifies whether the use of Spring Security's pre and post invocation annotations (@PreFilter, @PreAuthorize, @PostFilter, @PostAuthorize) should be enabled for this application context. Defaults to "true".
|
||||
attribute pre-post-enabled {xsd:boolean}?
|
||||
|
||||
@@ -615,6 +615,8 @@
|
||||
there is a match, the beans will automatically be proxied and security authorization
|
||||
applied to the methods accordingly. Interceptors are invoked in the order specified in
|
||||
AuthorizationInterceptorsOrder. Use can create your own interceptors using Spring AOP.
|
||||
Also, annotation-based interception can be overridden by expressions listed in
|
||||
<protect-pointcut> elements.
|
||||
</xs:documentation>
|
||||
</xs:annotation>
|
||||
<xs:complexType>
|
||||
@@ -630,6 +632,17 @@
|
||||
<xs:attributeGroup ref="security:ref"/>
|
||||
</xs:complexType>
|
||||
</xs:element>
|
||||
<xs:element minOccurs="0" maxOccurs="unbounded" name="protect-pointcut">
|
||||
<xs:annotation>
|
||||
<xs:documentation>Defines a protected pointcut and the access control configuration attributes that apply to
|
||||
it. Every bean registered in the Spring application context that provides a method that
|
||||
matches the pointcut will receive security authorization.
|
||||
</xs:documentation>
|
||||
</xs:annotation>
|
||||
<xs:complexType>
|
||||
<xs:attributeGroup ref="security:protect-pointcut.attlist"/>
|
||||
</xs:complexType>
|
||||
</xs:element>
|
||||
</xs:sequence>
|
||||
<xs:attributeGroup ref="security:method-security.attlist"/>
|
||||
</xs:complexType>
|
||||
|
||||
@@ -202,8 +202,8 @@ msmds.attlist &= id?
|
||||
msmds.attlist &= use-expressions?
|
||||
|
||||
method-security =
|
||||
## Provides method security for all beans registered in the Spring application context. Specifically, beans will be scanned for matches with Spring Security annotations. Where there is a match, the beans will automatically be proxied and security authorization applied to the methods accordingly. Interceptors are invoked in the order specified in AuthorizationInterceptorsOrder. Use can create your own interceptors using Spring AOP.
|
||||
element method-security {method-security.attlist, expression-handler?}
|
||||
## Provides method security for all beans registered in the Spring application context. Specifically, beans will be scanned for matches with Spring Security annotations. Where there is a match, the beans will automatically be proxied and security authorization applied to the methods accordingly. Interceptors are invoked in the order specified in AuthorizationInterceptorsOrder. Use can create your own interceptors using Spring AOP. Also, annotation-based interception can be overridden by expressions listed in <protect-pointcut> elements.
|
||||
element method-security {method-security.attlist, expression-handler?, protect-pointcut*}
|
||||
method-security.attlist &=
|
||||
## Specifies whether the use of Spring Security's pre and post invocation annotations (@PreFilter, @PreAuthorize, @PostFilter, @PostAuthorize) should be enabled for this application context. Defaults to "true".
|
||||
attribute pre-post-enabled {xsd:boolean}?
|
||||
|
||||
@@ -615,6 +615,8 @@
|
||||
there is a match, the beans will automatically be proxied and security authorization
|
||||
applied to the methods accordingly. Interceptors are invoked in the order specified in
|
||||
AuthorizationInterceptorsOrder. Use can create your own interceptors using Spring AOP.
|
||||
Also, annotation-based interception can be overridden by expressions listed in
|
||||
<protect-pointcut> elements.
|
||||
</xs:documentation>
|
||||
</xs:annotation>
|
||||
<xs:complexType>
|
||||
@@ -630,6 +632,17 @@
|
||||
<xs:attributeGroup ref="security:ref"/>
|
||||
</xs:complexType>
|
||||
</xs:element>
|
||||
<xs:element minOccurs="0" maxOccurs="unbounded" name="protect-pointcut">
|
||||
<xs:annotation>
|
||||
<xs:documentation>Defines a protected pointcut and the access control configuration attributes that apply to
|
||||
it. Every bean registered in the Spring application context that provides a method that
|
||||
matches the pointcut will receive security authorization.
|
||||
</xs:documentation>
|
||||
</xs:annotation>
|
||||
<xs:complexType>
|
||||
<xs:attributeGroup ref="security:protect-pointcut.attlist"/>
|
||||
</xs:complexType>
|
||||
</xs:element>
|
||||
</xs:sequence>
|
||||
<xs:attributeGroup ref="security:method-security.attlist"/>
|
||||
</xs:complexType>
|
||||
@@ -3728,4 +3741,4 @@
|
||||
<xs:enumeration value="LAST"/>
|
||||
</xs:restriction>
|
||||
</xs:simpleType>
|
||||
</xs:schema>
|
||||
</xs:schema>
|
||||
Reference in New Issue
Block a user