Cwikius-Spring/spring-security
1
0
Fork 0
mirror of https://github.com/spring-projects/spring-security.git synced 2025-07-16 15:23:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

SEC-733: Changed names of <global-method-security> attributes as discussed with Ben and updated sample to reflect the changes. Also changed explicit instantiation of Jsr250 and Secured annotation MethodDefinitionSource beans in GlobalMethodSecurityBDP into bean definitions to make more tooling friendly.

Browse Source
This commit is contained in:
Luke Taylor 2008-03-26 21:48:24 +00:00
parent 9ea2408ac6
commit ef5b3e2f9c
6 changed files with 2051 additions and 1920 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
core-tiger/src/test/resources/org/springframework/security/config/jsr250-annotated-method-security.xml
View File

@ -8,7 +8,7 @@ http://www.springframework.org/schema/security http://www.springframework.org/sc
<b:bean id="target" class="org.springframework.security.annotation.Jsr250BusinessServiceImpl"/>
<global-method-security jsr250="true"/>
<global-method-security jsr250-annotations="enabled"/>
<authentication-provider>
<user-service>

2
core-tiger/src/test/resources/org/springframework/security/config/secured-annotated-method-security.xml
View File

@ -8,7 +8,7 @@ http://www.springframework.org/schema/security http://www.springframework.org/sc
<b:bean id="target" class="org.springframework.security.annotation.Jsr250BusinessServiceImpl"/>
<global-method-security secured="true"/>
<global-method-security secured-annotations="enabled"/>
<authentication-provider>
<user-service>

25
core/src/main/java/org/springframework/security/config/GlobalMethodSecurityBeanDefinitionParser.java
View File

@ -10,6 +10,8 @@ import org.springframework.aop.config.AopNamespaceUtils;
import org.springframework.beans.BeanUtils;
import org.springframework.beans.factory.config.BeanDefinition;
import org.springframework.beans.factory.config.RuntimeBeanReference;
import org.springframework.beans.factory.support.BeanDefinitionBuilder;
import org.springframework.beans.factory.support.ManagedList;
import org.springframework.beans.factory.support.RootBeanDefinition;
import org.springframework.beans.factory.xml.BeanDefinitionParser;
import org.springframework.beans.factory.xml.ParserContext;
@ -28,7 +30,6 @@ import org.w3c.dom.Element;
/**
* Processes the top-level "global-method-security" element.
*
*
* @author Ben Alex
* @version $Id$
*/
@ -41,16 +42,16 @@ class GlobalMethodSecurityBeanDefinitionParser implements BeanDefinitionParser {
private static final String ATT_ACCESS = "access";
private static final String ATT_EXPRESSION = "expression";
private static final String ATT_ACCESS_MGR = "access-decision-manager-ref";
private static final String ATT_USE_JSR250 = "jsr250";
private static final String ATT_USE_SECURED = "secured";
private static final String ATT_USE_JSR250 = "jsr250-annotations";
private static final String ATT_USE_SECURED = "secured-annotations";
private void validatePresent(String className) {
Assert.isTrue(ClassUtils.isPresent(className), "Cannot locate '" + className + "'");
}
public BeanDefinition parse(Element element, ParserContext parserContext) {
boolean useJsr250 = "true".equals(element.getAttribute(ATT_USE_JSR250));
boolean useSecured = "true".equals(element.getAttribute(ATT_USE_SECURED));
boolean useJsr250 = "enabled".equals(element.getAttribute(ATT_USE_JSR250));
boolean useSecured = "enabled".equals(element.getAttribute(ATT_USE_SECURED));
// Check the required classes are present
if (useSecured) {
@ -91,23 +92,15 @@ class GlobalMethodSecurityBeanDefinitionParser implements BeanDefinitionParser {
}
// Create our list of method metadata delegates
List delegates = new ArrayList();
ManagedList delegates = new ManagedList();
delegates.add(mapBasedMethodDefinitionSource);
if (useSecured) {
try {
delegates.add(BeanUtils.instantiateClass(ClassUtils.forName(SECURED_METHOD_DEFINITION_SOURCE_CLASS)));
} catch (ClassNotFoundException shouldNotHappen) {
throw new IllegalStateException(shouldNotHappen);
}
delegates.add(BeanDefinitionBuilder.rootBeanDefinition(SECURED_METHOD_DEFINITION_SOURCE_CLASS).getBeanDefinition());
}
if (useJsr250) {
try {
delegates.add(BeanUtils.instantiateClass(ClassUtils.forName(JSR_250_SECURITY_METHOD_DEFINITION_SOURCE_CLASS)));
} catch (ClassNotFoundException shouldNotHappen) {
throw new IllegalStateException(shouldNotHappen);
}
delegates.add(BeanDefinitionBuilder.rootBeanDefinition(JSR_250_SECURITY_METHOD_DEFINITION_SOURCE_CLASS).getBeanDefinition());
}
// Register our DelegatingMethodDefinitionSource

12
core/src/main/resources/org/springframework/security/config/spring-security-2.0.rnc
View File

@ -157,13 +157,13 @@ global-method-security =
## Provides method security for all beans registered in the Spring application context. Specifically, beans will be scanned for Spring Security annotations and/or matches with the ordered list of "protect-pointcut" sub-elements. Where there is a match, the beans will automatically be proxied and security authorization applied to the methods accordingly. If you use and enable all three sources of method security metadata (ie "protect-pointcut" declarations, @Secured and also JSR 250 security annotations), the metadata sources will be queried in that order. In practical terms, this enables you to use XML to override method security metadata expressed by way of @Secured annotations, with @Secured annotations overriding method security metadata expressed by JSR 250 annotations. It is perfectly acceptable to mix and match, with a given Java type using a combination of XML, @Secured and JSR 250 to express method security metadata (albeit on different methods).
element global-method-security {global-method-security.attlist, protect-pointcut*}
global-method-security.attlist &=
## Specifies that Spring Security's @Secured annotation should be used. Please ensure you have the spring-security-tiger-xxx.jar on the classpath. Defaults to false.
attribute secured {"false" | "true" }?
## Specifies whether the use of Spring Security's @Secured annotations should be enabled for this application context. Please ensure you have the spring-security-tiger-xxx.jar on the classpath. Defaults to "disabled".
attribute secured-annotations {"disabled" | "enabled" }?
global-method-security.attlist &=
## Specifies that JSR-250 style attributes are to be used (for example "RolesAllowed"). This will require the javax.annotation.security classes on the classpath. Defaults to false.
attribute jsr250 {"false" | "true" }?
## Specifies whether JSR-250 style attributes are to be used (for example "RolesAllowed"). This will require the javax.annotation.security classes on the classpath. Defaults to "disabled".
attribute jsr250-annotations {"disabled" | "enabled" }?
global-method-security.attlist &=
## Optional AccessDecisionManager bean ID to override the default.
## Optional AccessDecisionManager bean ID to override the default used for method security.
attribute access-decision-manager-ref {xsd:string}?
@ -311,7 +311,7 @@ anonymous =
## Adds support for automatically granting all anonymous web requests a particular principal identity and a corresponding granted authority.
element anonymous {anonymous.attlist}
anonymous.attlist &=
## The key used between the provider and filter. This generally does not need to be set. If unset, it will default to "doesNotMatter".
## The key shared between the provider and filter. This generally does not need to be set. If unset, it will default to "doesNotMatter".
attribute key {xsd:string}?
anonymous.attlist &=
## The username that should be assigned to the anonymous request. This allows the principal to be identified, which may be important for logging and auditing. if unset, defaults to "anonymousUser".

326
core/src/main/resources/org/springframework/security/config/spring-security-2.0.xsd
View File

@ -1,5 +1,7 @@
<?xml version="1.0" encoding="utf-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:security="http://www.springframework.org/schema/security" elementFormDefault="qualified" targetNamespace="http://www.springframework.org/schema/security">
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:security="http://www.springframework.org/schema/security" elementFormDefault="qualified"
targetNamespace="http://www.springframework.org/schema/security">
<xs:attributeGroup name="hash">
@ -7,7 +9,8 @@
<xs:annotation>
<xs:documentation>Defines the hashing algorithm used on user passwords. We recommend strongly against using MD4, as it is a very weak hashing algorithm.</xs:documentation>
<xs:documentation>Defines the hashing algorithm used on user passwords. We recommend
strongly against using MD4, as it is a very weak hashing algorithm.</xs:documentation>
</xs:annotation>
@ -67,7 +70,9 @@
<xs:annotation>
<xs:documentation>Defines the type of pattern used to specify URL paths (either JDK 1.4-compatible regular expressions, or Apache Ant expressions). Defaults to "ant" if unspecified.</xs:documentation>
<xs:documentation>Defines the type of pattern used to specify URL paths (either JDK
1.4-compatible regular expressions, or Apache Ant expressions). Defaults to "ant" if
unspecified.</xs:documentation>
</xs:annotation>
@ -93,7 +98,8 @@
<xs:annotation>
<xs:documentation>Specifies an IP port number. Used to configure an embedded LDAP server, for example.</xs:documentation>
<xs:documentation>Specifies an IP port number. Used to configure an embedded LDAP server,
for example.</xs:documentation>
</xs:annotation>
@ -121,7 +127,8 @@
<xs:annotation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the context.</xs:documentation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the
context.</xs:documentation>
</xs:annotation>
@ -160,7 +167,8 @@
<xs:element name="password-encoder">
<xs:annotation>
<xs:documentation>element which defines a password encoding strategy. Used by an authentication provider to convert submitted passwords to hashed versions, for example.</xs:documentation>
<xs:documentation>element which defines a password encoding strategy. Used by an
authentication provider to convert submitted passwords to hashed versions, for example.</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -174,7 +182,8 @@
<xs:annotation>
<xs:documentation>A property of the UserDetails object which will be used as salt by a password encoder. Typically something like "username" might be used. </xs:documentation>
<xs:documentation>A property of the UserDetails object which will be used as salt by
a password encoder. Typically something like "username" might be used. </xs:documentation>
</xs:annotation>
@ -184,7 +193,8 @@
<xs:annotation>
<xs:documentation>A single value that will be used as the salt for a password encoder. </xs:documentation>
<xs:documentation>A single value that will be used as the salt for a password
encoder. </xs:documentation>
</xs:annotation>
@ -216,7 +226,8 @@
<xs:annotation>
<xs:documentation>Defines the hashing algorithm used on user passwords. We recommend strongly against using MD4, as it is a very weak hashing algorithm.</xs:documentation>
<xs:documentation>Defines the hashing algorithm used on user passwords. We recommend
strongly against using MD4, as it is a very weak hashing algorithm.</xs:documentation>
</xs:annotation>
@ -273,7 +284,8 @@
<xs:annotation>
<xs:documentation>A property of the UserDetails object which will be used as salt by a password encoder. Typically something like "username" might be used. </xs:documentation>
<xs:documentation>A property of the UserDetails object which will be used as salt by a
password encoder. Typically something like "username" might be used. </xs:documentation>
</xs:annotation>
@ -298,7 +310,10 @@
<xs:element name="ldap-server">
<xs:annotation>
<xs:documentation>Defines an LDAP server location or starts an embedded server. The url indicates the location of a remote server. If no url is given, an embedded server will be started, listening on the supplied port number. The port is optional and defaults to 33389. A Spring LDAP ContextSource bean will be registered for the server with the id supplied. </xs:documentation>
<xs:documentation>Defines an LDAP server location or starts an embedded server. The url
indicates the location of a remote server. If no url is given, an embedded server will be
started, listening on the supplied port number. The port is optional and defaults to 33389.
A Spring LDAP ContextSource bean will be registered for the server with the id supplied. </xs:documentation>
</xs:annotation>
<xs:complexType>
@ -314,7 +329,8 @@
<xs:annotation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the context.</xs:documentation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the
context.</xs:documentation>
</xs:annotation>
@ -334,7 +350,8 @@
<xs:annotation>
<xs:documentation>Specifies an IP port number. Used to configure an embedded LDAP server, for example.</xs:documentation>
<xs:documentation>Specifies an IP port number. Used to configure an embedded LDAP server,
for example.</xs:documentation>
</xs:annotation>
@ -344,7 +361,8 @@
<xs:annotation>
<xs:documentation>Username (DN) of the "manager" user identity which will be used to authenticate to a (non-embedded) LDAP server. If omitted, anonymous access will be used. </xs:documentation>
<xs:documentation>Username (DN) of the "manager" user identity which will be used to
authenticate to a (non-embedded) LDAP server. If omitted, anonymous access will be used. </xs:documentation>
</xs:annotation>
@ -356,7 +374,8 @@
<xs:annotation>
<xs:documentation>Explicitly specifies an ldif file resource to load into an embedded LDAP server</xs:documentation>
<xs:documentation>Explicitly specifies an ldif file resource to load into an embedded LDAP
server</xs:documentation>
</xs:annotation>
@ -366,7 +385,8 @@
<xs:annotation>
<xs:documentation>Optional root suffix for the embedded LDAP server. Default is "dc=springframework,dc=org"</xs:documentation>
<xs:documentation>Optional root suffix for the embedded LDAP server. Default is
"dc=springframework,dc=org"</xs:documentation>
</xs:annotation>
@ -380,7 +400,8 @@
<xs:annotation>
<xs:documentation>The optional server to use. If omitted, and a default LDAP server is registered (using &lt;ldap-server&gt; with no Id), that server will be used. </xs:documentation>
<xs:documentation>The optional server to use. If omitted, and a default LDAP server is
registered (using &lt;ldap-server&gt; with no Id), that server will be used. </xs:documentation>
</xs:annotation>
@ -394,7 +415,8 @@
<xs:annotation>
<xs:documentation>Group search filter. Defaults to (uniqueMember={0}). The substituted parameter is the DN of the user.</xs:documentation>
<xs:documentation>Group search filter. Defaults to (uniqueMember={0}). The substituted
parameter is the DN of the user.</xs:documentation>
</xs:annotation>
@ -442,7 +464,8 @@
<xs:annotation>
<xs:documentation>The LDAP attribute name which contains the role name which will be used within Spring Security. Defaults to "cn".</xs:documentation>
<xs:documentation>The LDAP attribute name which contains the role name which will be used
within Spring Security. Defaults to "cn".</xs:documentation>
</xs:annotation>
@ -464,7 +487,8 @@
<xs:annotation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the context.</xs:documentation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the
context.</xs:documentation>
</xs:annotation>
@ -474,7 +498,8 @@
<xs:annotation>
<xs:documentation>The optional server to use. If omitted, and a default LDAP server is registered (using &lt;ldap-server&gt; with no Id), that server will be used. </xs:documentation>
<xs:documentation>The optional server to use. If omitted, and a default LDAP server is
registered (using &lt;ldap-server&gt; with no Id), that server will be used. </xs:documentation>
</xs:annotation>
@ -488,7 +513,8 @@
<xs:annotation>
<xs:documentation>Group search filter. Defaults to (uniqueMember={0}). The substituted parameter is the DN of the user.</xs:documentation>
<xs:documentation>Group search filter. Defaults to (uniqueMember={0}). The substituted
parameter is the DN of the user.</xs:documentation>
</xs:annotation>
@ -508,7 +534,8 @@
<xs:annotation>
<xs:documentation>The LDAP attribute name which contains the role name which will be used within Spring Security. Defaults to "cn".</xs:documentation>
<xs:documentation>The LDAP attribute name which contains the role name which will be used
within Spring Security. Defaults to "cn".</xs:documentation>
</xs:annotation>
@ -541,7 +568,8 @@
<xs:annotation>
<xs:documentation>The optional server to use. If omitted, and a default LDAP server is registered (using &lt;ldap-server&gt; with no Id), that server will be used. </xs:documentation>
<xs:documentation>The optional server to use. If omitted, and a default LDAP server is
registered (using &lt;ldap-server&gt; with no Id), that server will be used. </xs:documentation>
</xs:annotation>
@ -565,7 +593,8 @@
<xs:annotation>
<xs:documentation>Group search filter. Defaults to (uniqueMember={0}). The substituted parameter is the DN of the user.</xs:documentation>
<xs:documentation>Group search filter. Defaults to (uniqueMember={0}). The substituted
parameter is the DN of the user.</xs:documentation>
</xs:annotation>
@ -575,7 +604,8 @@
<xs:annotation>
<xs:documentation>The LDAP attribute name which contains the role name which will be used within Spring Security. Defaults to "cn".</xs:documentation>
<xs:documentation>The LDAP attribute name which contains the role name which will be used
within Spring Security. Defaults to "cn".</xs:documentation>
</xs:annotation>
@ -585,7 +615,9 @@
<xs:annotation>
<xs:documentation>A specific pattern used to build the user's DN, for example "uid={0},ou=people". The key "{0}" must be present and will be substituted with the username.</xs:documentation>
<xs:documentation>A specific pattern used to build the user's DN, for example
"uid={0},ou=people". The key "{0}" must be present and will be substituted with the
username.</xs:documentation>
</xs:annotation>
@ -596,7 +628,8 @@
<xs:element name="password-compare">
<xs:annotation>
<xs:documentation>Specifies that an LDAP provider should use an LDAP compare operation of the user's password to authenticate the user</xs:documentation>
<xs:documentation>Specifies that an LDAP provider should use an LDAP compare operation of the
user's password to authenticate the user</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -618,7 +651,8 @@
<xs:annotation>
<xs:documentation>The attribute in the directory which contains the user password. Defaults to "userPassword".</xs:documentation>
<xs:documentation>The attribute in the directory which contains the user password. Defaults
to "userPassword".</xs:documentation>
</xs:annotation>
@ -628,7 +662,8 @@
<xs:annotation>
<xs:documentation>Defines the hashing algorithm used on user passwords. We recommend strongly against using MD4, as it is a very weak hashing algorithm.</xs:documentation>
<xs:documentation>Defines the hashing algorithm used on user passwords. We recommend
strongly against using MD4, as it is a very weak hashing algorithm.</xs:documentation>
</xs:annotation>
@ -659,7 +694,8 @@
<xs:element name="intercept-methods">
<xs:annotation>
<xs:documentation>Can be used inside a bean definition to add a security interceptor to the bean and set up access configuration attributes for the bean's methods</xs:documentation>
<xs:documentation>Can be used inside a bean definition to add a security interceptor to the
bean and set up access configuration attributes for the bean's methods</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -681,7 +717,8 @@
<xs:annotation>
<xs:documentation>Optional AccessDecisionManager bean ID to be used by the created method security interceptor.</xs:documentation>
<xs:documentation>Optional AccessDecisionManager bean ID to be used by the created method
security interceptor.</xs:documentation>
</xs:annotation>
@ -692,7 +729,9 @@
<xs:element name="protect">
<xs:annotation>
<xs:documentation>Defines a protected method and the access control configuration attributes that apply to it. We strongly advise you NOT to mix "protect" declarations with any services provided "global-method-security".</xs:documentation>
<xs:documentation>Defines a protected method and the access control configuration attributes
that apply to it. We strongly advise you NOT to mix "protect" declarations with any services
provided "global-method-security".</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -718,7 +757,8 @@
<xs:annotation>
<xs:documentation>Access configuration attributes list that applies to the method, e.g. "ROLE_A,ROLE_B".</xs:documentation>
<xs:documentation>Access configuration attributes list that applies to the method, e.g.
"ROLE_A,ROLE_B".</xs:documentation>
</xs:annotation>
@ -729,7 +769,17 @@
<xs:element name="global-method-security">
<xs:annotation>
<xs:documentation>Provides method security for all beans registered in the Spring application context. Specifically, beans will be scanned for Spring Security annotations and/or matches with the ordered list of "protect-pointcut" sub-elements. Where there is a match, the beans will automatically be proxied and security authorization applied to the methods accordingly. If you use and enable all three sources of method security metadata (ie "protect-pointcut" declarations, @Secured and also JSR 250 security annotations), the metadata sources will be queried in that order. In practical terms, this enables you to use XML to override method security metadata expressed by way of @Secured annotations, with @Secured annotations overriding method security metadata expressed by JSR 250 annotations. It is perfectly acceptable to mix and match, with a given Java type using a combination of XML, @Secured and JSR 250 to express method security metadata (albeit on different methods).</xs:documentation>
<xs:documentation>Provides method security for all beans registered in the Spring application
context. Specifically, beans will be scanned for Spring Security annotations and/or matches
with the ordered list of "protect-pointcut" sub-elements. Where there is a match, the beans
will automatically be proxied and security authorization applied to the methods accordingly.
If you use and enable all three sources of method security metadata (ie "protect-pointcut"
declarations, @Secured and also JSR 250 security annotations), the metadata sources will be
queried in that order. In practical terms, this enables you to use XML to override method
security metadata expressed by way of @Secured annotations, with @Secured annotations
overriding method security metadata expressed by JSR 250 annotations. It is perfectly
acceptable to mix and match, with a given Java type using a combination of XML, @Secured and
JSR 250 to express method security metadata (albeit on different methods).</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -739,7 +789,9 @@
<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: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>
@ -758,11 +810,13 @@
<xs:attributeGroup name="global-method-security.attlist">
<xs:attribute name="secured">
<xs:attribute name="secured-annotations">
<xs:annotation>
<xs:documentation>Specifies that Spring Security's @Secured annotation should be used. Please ensure you have the spring-security-tiger-xxx.jar on the classpath. Defaults to false.</xs:documentation>
<xs:documentation>Specifies whether the use of Spring Security's @Secured annotations should
be enabled for this application context. Please ensure you have the
spring-security-tiger-xxx.jar on the classpath. Defaults to "disabled".</xs:documentation>
</xs:annotation>
@ -770,9 +824,9 @@
<xs:restriction base="xs:token">
<xs:enumeration value="false"/>
<xs:enumeration value="disabled"/>
<xs:enumeration value="true"/>
<xs:enumeration value="enabled"/>
</xs:restriction>
@ -780,11 +834,13 @@
</xs:attribute>
<xs:attribute name="jsr250">
<xs:attribute name="jsr250-annotations">
<xs:annotation>
<xs:documentation>Specifies that JSR-250 style attributes are to be used (for example "RolesAllowed"). This will require the javax.annotation.security classes on the classpath. Defaults to false.</xs:documentation>
<xs:documentation>Specifies whether JSR-250 style attributes are to be used (for example
"RolesAllowed"). This will require the javax.annotation.security classes on the classpath.
Defaults to "disabled".</xs:documentation>
</xs:annotation>
@ -792,9 +848,9 @@
<xs:restriction base="xs:token">
<xs:enumeration value="false"/>
<xs:enumeration value="disabled"/>
<xs:enumeration value="true"/>
<xs:enumeration value="enabled"/>
</xs:restriction>
@ -806,7 +862,8 @@
<xs:annotation>
<xs:documentation>Optional AccessDecisionManager bean ID to override the default.</xs:documentation>
<xs:documentation>Optional AccessDecisionManager bean ID to override the default used for
method security.</xs:documentation>
</xs:annotation>
@ -821,7 +878,8 @@
<xs:annotation>
<xs:documentation>An AspectJ expression, including the 'execution' keyword. For example, 'execution(int com.foo.TargetObject.countLength(String))' (without the quotes).</xs:documentation>
<xs:documentation>An AspectJ expression, including the 'execution' keyword. For example,
'execution(int com.foo.TargetObject.countLength(String))' (without the quotes).</xs:documentation>
</xs:annotation>
@ -831,7 +889,8 @@
<xs:annotation>
<xs:documentation>Access configuration attributes list that applies to all methods matching the pointcut, e.g. "ROLE_A,ROLE_B"</xs:documentation>
<xs:documentation>Access configuration attributes list that applies to all methods matching
the pointcut, e.g. "ROLE_A,ROLE_B"</xs:documentation>
</xs:annotation>
@ -852,7 +911,8 @@
<xs:element name="intercept-url">
<xs:annotation>
<xs:documentation>Specifies the access attributes and/or filter list for a particular set of URLs.</xs:documentation>
<xs:documentation>Specifies the access attributes and/or filter list for a particular
set of URLs.</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -865,7 +925,8 @@
<xs:element name="form-login">
<xs:annotation>
<xs:documentation>Sets up a form login configuration for authentication with a username and password</xs:documentation>
<xs:documentation>Sets up a form login configuration for authentication with a username
and password</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -893,7 +954,8 @@
<xs:element name="http-basic">
<xs:annotation>
<xs:documentation>Adds support for basic authentication (this is an element to permit future expansion, such as supporting an "ignoreFailure" attribute)</xs:documentation>
<xs:documentation>Adds support for basic authentication (this is an element to permit
future expansion, such as supporting an "ignoreFailure" attribute)</xs:documentation>
</xs:annotation>
<xs:complexType/>
@ -902,7 +964,9 @@
<xs:element name="logout">
<xs:annotation>
<xs:documentation>Incorporates a logout processing filter. Most web applications require a logout filter, although you may not require one if you write a controller to provider similar logic.</xs:documentation>
<xs:documentation>Incorporates a logout processing filter. Most web applications require
a logout filter, although you may not require one if you write a controller to
provider similar logic.</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -915,7 +979,8 @@
<xs:element name="concurrent-session-control">
<xs:annotation>
<xs:documentation>Adds support for concurrent session control, allowing limits to be placed on the number of sessions a user can have.</xs:documentation>
<xs:documentation>Adds support for concurrent session control, allowing limits to be
placed on the number of sessions a user can have.</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -936,7 +1001,8 @@
<xs:element name="anonymous">
<xs:annotation>
<xs:documentation>Adds support for automatically granting all anonymous web requests a particular principal identity and a corresponding granted authority.</xs:documentation>
<xs:documentation>Adds support for automatically granting all anonymous web requests a
particular principal identity and a corresponding granted authority.</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -949,7 +1015,8 @@
<xs:element name="port-mappings">
<xs:annotation>
<xs:documentation>Defines the list of mappings between http and https ports for use in redirects</xs:documentation>
<xs:documentation>Defines the list of mappings between http and https ports for use in
redirects</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -976,7 +1043,11 @@
<xs:annotation>
<xs:documentation>Automatically registers a login form, BASIC authentication, anonymous authentication, logout services, remember-me and servlet-api-integration. If set to "true", all of these capabilities are added (although you can still customize the configuration of each by providing the respective element). If unspecified, defaults to "false".</xs:documentation>
<xs:documentation>Automatically registers a login form, BASIC authentication, anonymous
authentication, logout services, remember-me and servlet-api-integration. If set to
"true", all of these capabilities are added (although you can still customize the
configuration of each by providing the respective element). If unspecified, defaults to
"false".</xs:documentation>
</xs:annotation>
@ -998,7 +1069,8 @@
<xs:annotation>
<xs:documentation>Controls the eagerness with which an HTTP session is created. If not set, defaults to "ifRequired".</xs:documentation>
<xs:documentation>Controls the eagerness with which an HTTP session is created. If not set,
defaults to "ifRequired".</xs:documentation>
</xs:annotation>
@ -1022,7 +1094,9 @@
<xs:annotation>
<xs:documentation>Defines the type of pattern used to specify URL paths (either JDK 1.4-compatible regular expressions, or Apache Ant expressions). Defaults to "ant" if unspecified.</xs:documentation>
<xs:documentation>Defines the type of pattern used to specify URL paths (either JDK
1.4-compatible regular expressions, or Apache Ant expressions). Defaults to "ant" if
unspecified.</xs:documentation>
</xs:annotation>
@ -1044,7 +1118,8 @@
<xs:annotation>
<xs:documentation>Whether test URLs should be converted to lower case prior to comparing with defined path patterns. If unspecified, defaults to "true".</xs:documentation>
<xs:documentation>Whether test URLs should be converted to lower case prior to comparing
with defined path patterns. If unspecified, defaults to "true".</xs:documentation>
</xs:annotation>
@ -1066,7 +1141,9 @@
<xs:annotation>
<xs:documentation>Provides versions of HttpServletRequest security methods such as isUserInRole() and getPrincipal() which are implemented by accessing the Spring SecurityContext. Defaults to "true".</xs:documentation>
<xs:documentation>Provides versions of HttpServletRequest security methods such as
isUserInRole() and getPrincipal() which are implemented by accessing the Spring
SecurityContext. Defaults to "true".</xs:documentation>
</xs:annotation>
@ -1088,7 +1165,8 @@
<xs:annotation>
<xs:documentation>Optional attribute specifying the ID of the AccessDecisionManager implementation which should be used for authorizing HTTP requests.</xs:documentation>
<xs:documentation>Optional attribute specifying the ID of the AccessDecisionManager
implementation which should be used for authorizing HTTP requests.</xs:documentation>
</xs:annotation>
@ -1098,7 +1176,9 @@
<xs:annotation>
<xs:documentation>Optional attribute specifying the realm name that will be used for all authentication features that require a realm name (eg BASIC and Digest authentication). If unspecified, defaults to "Spring Security Application".</xs:documentation>
<xs:documentation>Optional attribute specifying the realm name that will be used for all
authentication features that require a realm name (eg BASIC and Digest authentication). If
unspecified, defaults to "Spring Security Application".</xs:documentation>
</xs:annotation>
@ -1108,7 +1188,10 @@
<xs:annotation>
<xs:documentation>Indicates whether an existing session should be invalidated when a user authenticates and a new session started. If set to "none" no change will be made. "newSession" will create a new empty session. "migrateSession" will create a new session and copy the session attributes to the new session. Defaults to "migrateSession".</xs:documentation>
<xs:documentation>Indicates whether an existing session should be invalidated when a user
authenticates and a new session started. If set to "none" no change will be made.
"newSession" will create a new empty session. "migrateSession" will create a new session
and copy the session attributes to the new session. Defaults to "migrateSession".</xs:documentation>
</xs:annotation>
@ -1137,7 +1220,8 @@
<xs:annotation>
<xs:documentation>The pattern which defines the URL path. The content will depend on the type set in the containing http element, so will default to ant path syntax.</xs:documentation>
<xs:documentation>The pattern which defines the URL path. The content will depend on the
type set in the containing http element, so will default to ant path syntax.</xs:documentation>
</xs:annotation>
@ -1157,7 +1241,8 @@
<xs:annotation>
<xs:documentation>The HTTP Method for which the access configuration attributes should apply. If not specified, the attributes will apply to any method.</xs:documentation>
<xs:documentation>The HTTP Method for which the access configuration attributes should
apply. If not specified, the attributes will apply to any method.</xs:documentation>
</xs:annotation>
@ -1189,7 +1274,9 @@
<xs:annotation>
<xs:documentation>The filter list for the path. Currently can be set to "none" to remove a path from having any filters applied. The full filter stack (consisting of all defined filters, will be applied to any other paths).</xs:documentation>
<xs:documentation>The filter list for the path. Currently can be set to "none" to remove a
path from having any filters applied. The full filter stack (consisting of all defined
filters, will be applied to any other paths).</xs:documentation>
</xs:annotation>
@ -1238,7 +1325,9 @@
<xs:annotation>
<xs:documentation>Specifies the URL that will cause a logout. Spring Security will initialize a filter that responds to this particular URL. Defaults to /j_spring_security_logout if unspecified.</xs:documentation>
<xs:documentation>Specifies the URL that will cause a logout. Spring Security will
initialize a filter that responds to this particular URL. Defaults to
/j_spring_security_logout if unspecified.</xs:documentation>
</xs:annotation>
@ -1248,7 +1337,8 @@
<xs:annotation>
<xs:documentation>Specifies the URL to display once the user has logged out. If not specified, defaults to /.</xs:documentation>
<xs:documentation>Specifies the URL to display once the user has logged out. If not
specified, defaults to /.</xs:documentation>
</xs:annotation>
@ -1258,7 +1348,8 @@
<xs:annotation>
<xs:documentation>Specifies whether a logout also causes HttpSession invalidation, which is generally desirable. If unspecified, defaults to true.</xs:documentation>
<xs:documentation>Specifies whether a logout also causes HttpSession invalidation, which is
generally desirable. If unspecified, defaults to true.</xs:documentation>
</xs:annotation>
@ -1285,7 +1376,8 @@
<xs:annotation>
<xs:documentation>The URL that the login form is posted to. If unspecified, it defaults to /j_spring_security_check.</xs:documentation>
<xs:documentation>The URL that the login form is posted to. If unspecified, it defaults to
/j_spring_security_check.</xs:documentation>
</xs:annotation>
@ -1295,7 +1387,10 @@
<xs:annotation>
<xs:documentation>The URL that will be redirected to after successful authentication, if the user's previous action could not be resumed. This generally happens if the user visits a login page without having first requested a secured operation that triggers authentication. If unspecified, defaults to the root of the application.</xs:documentation>
<xs:documentation>The URL that will be redirected to after successful authentication, if the
user's previous action could not be resumed. This generally happens if the user visits a
login page without having first requested a secured operation that triggers
authentication. If unspecified, defaults to the root of the application.</xs:documentation>
</xs:annotation>
@ -1305,7 +1400,9 @@
<xs:annotation>
<xs:documentation>The URL for the login page. If no login URL is specified, Spring Security will automatically create a login URL at /spring_security_login and a corresponding filter to render that login URL when requested.</xs:documentation>
<xs:documentation>The URL for the login page. If no login URL is specified, Spring Security
will automatically create a login URL at /spring_security_login and a corresponding filter
to render that login URL when requested.</xs:documentation>
</xs:annotation>
@ -1315,7 +1412,10 @@
<xs:annotation>
<xs:documentation>The URL for the login failure page. If no login failure URL is specified, Spring Security will automatically create a failure login URL at /spring_security_login?login_error and a corresponding filter to render that login failure URL when requested.</xs:documentation>
<xs:documentation>The URL for the login failure page. If no login failure URL is specified,
Spring Security will automatically create a failure login URL at
/spring_security_login?login_error and a corresponding filter to render that login failure
URL when requested.</xs:documentation>
</xs:annotation>
@ -1349,7 +1449,8 @@
<xs:element name="filter-chain-map">
<xs:annotation>
<xs:documentation>Used to explicitly configure a FilterChainProxy instance with a FilterChainMap</xs:documentation>
<xs:documentation>Used to explicitly configure a FilterChainProxy instance with a
FilterChainMap</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -1359,7 +1460,10 @@
<xs:element maxOccurs="unbounded" name="filter-chain">
<xs:annotation>
<xs:documentation>Used within filter-chain-map to define a specific URL pattern and the list of filters which apply to the URLs matching that pattern. When multiple filter-chain elements are used within a filter-chain-map element, the most specific patterns must be placed at the top of the list, with most general ones at the bottom.</xs:documentation>
<xs:documentation>Used within filter-chain-map to define a specific URL pattern and the
list of filters which apply to the URLs matching that pattern. When multiple
filter-chain elements are used within a filter-chain-map element, the most specific
patterns must be placed at the top of the list, with most general ones at the bottom.</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -1394,7 +1498,11 @@
<xs:element name="filter-invocation-definition-source">
<xs:annotation>
<xs:documentation>Used to explicitly configure a FilterInvocationDefinitionSource bean for use with a FilterSecurityInterceptor. Usually only needed if you are configuring a FilterChainProxy explicitly, rather than using the &lt;http&gt; element. The intercept-url elements used should only contain pattern, method and access attributes. Any others will result in a configuration error. </xs:documentation>
<xs:documentation>Used to explicitly configure a FilterInvocationDefinitionSource bean for use
with a FilterSecurityInterceptor. Usually only needed if you are configuring a
FilterChainProxy explicitly, rather than using the &lt;http&gt; element. The
intercept-url elements used should only contain pattern, method and access attributes. Any
others will result in a configuration error. </xs:documentation>
</xs:annotation>
<xs:complexType>
@ -1404,7 +1512,8 @@
<xs:element maxOccurs="unbounded" name="intercept-url">
<xs:annotation>
<xs:documentation>Specifies the access attributes and/or filter list for a particular set of URLs.</xs:documentation>
<xs:documentation>Specifies the access attributes and/or filter list for a particular
set of URLs.</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -1427,7 +1536,8 @@
<xs:annotation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the context.</xs:documentation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the
context.</xs:documentation>
</xs:annotation>
@ -1459,7 +1569,9 @@
<xs:annotation>
<xs:documentation>Defines the type of pattern used to specify URL paths (either JDK 1.4-compatible regular expressions, or Apache Ant expressions). Defaults to "ant" if unspecified.</xs:documentation>
<xs:documentation>Defines the type of pattern used to specify URL paths (either JDK
1.4-compatible regular expressions, or Apache Ant expressions). Defaults to "ant" if
unspecified.</xs:documentation>
</xs:annotation>
@ -1523,7 +1635,8 @@
<xs:annotation>
<xs:documentation>The key used between the provider and filter. This generally does not need to be set. If unset, it will default to "doesNotMatter".</xs:documentation>
<xs:documentation>The key shared between the provider and filter. This generally does not
need to be set. If unset, it will default to "doesNotMatter".</xs:documentation>
</xs:annotation>
@ -1533,7 +1646,9 @@
<xs:annotation>
<xs:documentation>The username that should be assigned to the anonymous request. This allows the principal to be identified, which may be important for logging and auditing. if unset, defaults to "anonymousUser".</xs:documentation>
<xs:documentation>The username that should be assigned to the anonymous request. This allows
the principal to be identified, which may be important for logging and auditing. if unset,
defaults to "anonymousUser".</xs:documentation>
</xs:annotation>
@ -1543,7 +1658,9 @@
<xs:annotation>
<xs:documentation>The granted authority that should be assigned to the anonymous request. Commonly this is used to assign the anonymous request particular roles, which can subsequently be used in authorization decisions. If unset, defaults to "ROLE_ANONYMOUS".</xs:documentation>
<xs:documentation>The granted authority that should be assigned to the anonymous request.
Commonly this is used to assign the anonymous request particular roles, which can
subsequently be used in authorization decisions. If unset, defaults to "ROLE_ANONYMOUS".</xs:documentation>
</xs:annotation>
@ -1581,7 +1698,8 @@
<xs:annotation>
<xs:documentation>The regular expression used to obtain the username from the certificate's subject. Defaults to matching on the common name using the pattern "CN=(.*?),".</xs:documentation>
<xs:documentation>The regular expression used to obtain the username from the certificate's
subject. Defaults to matching on the common name using the pattern "CN=(.*?),".</xs:documentation>
</xs:annotation>
@ -1602,7 +1720,9 @@
<xs:element name="authentication-manager">
<xs:annotation>
<xs:documentation>If you are using namespace configuration with Spring Security, an AuthenticationManager will automatically be registered. This element simple allows you to define an alias to allow you to reference the authentication-manager in your own beans. </xs:documentation>
<xs:documentation>If you are using namespace configuration with Spring Security, an
AuthenticationManager will automatically be registered. This element simple allows you to
define an alias to allow you to reference the authentication-manager in your own beans. </xs:documentation>
</xs:annotation>
<xs:complexType>
@ -1627,7 +1747,8 @@
<xs:element name="authentication-provider">
<xs:annotation>
<xs:documentation>Indicates that the contained user-service should be used as an authentication source. </xs:documentation>
<xs:documentation>Indicates that the contained user-service should be used as an
authentication source. </xs:documentation>
</xs:annotation>
<xs:complexType>
@ -1666,7 +1787,8 @@
<xs:element name="user-service" substitutionGroup="security:any-user-service">
<xs:annotation>
<xs:documentation>Creates an in-memory UserDetailsService from a properties file or a list of "user" child elements.</xs:documentation>
<xs:documentation>Creates an in-memory UserDetailsService from a properties file or a list of
"user" child elements.</xs:documentation>
</xs:annotation>
<xs:complexType>
@ -1681,7 +1803,8 @@
<xs:annotation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the context.</xs:documentation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the
context.</xs:documentation>
</xs:annotation>
@ -1727,7 +1850,9 @@
<xs:annotation>
<xs:documentation>The password assigned to the user. This may be hashed if the corresponding authentication provider supports hashing (remember to set the "hash" attribute of the "user-service" element).</xs:documentation>
<xs:documentation>The password assigned to the user. This may be hashed if the corresponding
authentication provider supports hashing (remember to set the "hash" attribute of the
"user-service" element).</xs:documentation>
</xs:annotation>
@ -1737,7 +1862,8 @@
<xs:annotation>
<xs:documentation>One of more authorities granted to the user. Separate authorities with a comma (but no space). For example, "ROLE_USER,ROLE_ADMINISTRATOR"</xs:documentation>
<xs:documentation>One of more authorities granted to the user. Separate authorities with a
comma (but no space). For example, "ROLE_USER,ROLE_ADMINISTRATOR"</xs:documentation>
</xs:annotation>
@ -1779,7 +1905,8 @@
<xs:annotation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the context.</xs:documentation>
<xs:documentation>A bean identifier, used for referring to the bean elsewhere in the
context.</xs:documentation>
</xs:annotation>
@ -1819,7 +1946,9 @@
<xs:element name="custom-filter">
<xs:annotation>
<xs:documentation>Used to indicate that a filter bean declaration should be incorporated into the security filter chain. If neither the 'after' or 'before' options are supplied, then the filter must implement the Ordered interface directly. </xs:documentation>
<xs:documentation>Used to indicate that a filter bean declaration should be incorporated into
the security filter chain. If neither the 'after' or 'before' options are supplied, then the
filter must implement the Ordered interface directly. </xs:documentation>
</xs:annotation>
<xs:complexType>
@ -1828,7 +1957,11 @@
<xs:annotation>
<xs:documentation>The filter immediately after which the custom-filter should be placed in the chain. This feature will only be needed by advanced users who wish to mix their own filters into the security filter chain and have some knowledge of the standard Spring Security filters. The filter names map to specific Spring Security implementation filters. </xs:documentation>
<xs:documentation>The filter immediately after which the custom-filter should be placed in
the chain. This feature will only be needed by advanced users who wish to mix their own
filters into the security filter chain and have some knowledge of the standard Spring
Security filters. The filter names map to specific Spring Security implementation
filters. </xs:documentation>
</xs:annotation>
@ -1838,7 +1971,8 @@
<xs:annotation>
<xs:documentation>The filter immediately before which the custom-filter should be placed in the chain</xs:documentation>
<xs:documentation>The filter immediately before which the custom-filter should be placed
in the chain</xs:documentation>
</xs:annotation>
@ -1853,7 +1987,10 @@
<xs:annotation>
<xs:documentation>The filter immediately after which the custom-filter should be placed in the chain. This feature will only be needed by advanced users who wish to mix their own filters into the security filter chain and have some knowledge of the standard Spring Security filters. The filter names map to specific Spring Security implementation filters. </xs:documentation>
<xs:documentation>The filter immediately after which the custom-filter should be placed in
the chain. This feature will only be needed by advanced users who wish to mix their own
filters into the security filter chain and have some knowledge of the standard Spring
Security filters. The filter names map to specific Spring Security implementation filters. </xs:documentation>
</xs:annotation>
@ -1867,7 +2004,8 @@
<xs:annotation>
<xs:documentation>The filter immediately before which the custom-filter should be placed in the chain</xs:documentation>
<xs:documentation>The filter immediately before which the custom-filter should be placed in
the chain</xs:documentation>
</xs:annotation>

2
samples/tutorial/src/main/webapp/WEB-INF/applicationContext-security-ns.xml
View File

@ -12,7 +12,7 @@
xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-2.0.xsd
http://www.springframework.org/schema/security http://www.springframework.org/schema/security/spring-security-2.0.xsd">
<global-method-security secured="true"/>
<global-method-security secured-annotations="enabled"/>
<http>
<intercept-url pattern="/secure/extreme/**" access="ROLE_SUPERVISOR"/>