sub-element
+ Map pointcutMap = new LinkedHashMap();
+ List protect = DomUtils.getChildElementsByTagName(element, Elements.PROTECT_POINTCUT);
+
+ for (Iterator i = protect.iterator(); i.hasNext();) {
+ Element childElt = (Element) i.next();
+ String accessConfig = childElt.getAttribute(ATT_ACCESS);
+ String expression = childElt.getAttribute(ATT_EXPRESSION);
+ Assert.hasText(accessConfig, "Access configuration required for '" + childElt + "'");
+ Assert.hasText(expression, "Expression required for '" + childElt + "'");
+
+ ConfigAttributeDefinition def = new ConfigAttributeDefinition(StringUtils.commaDelimitedListToStringArray(accessConfig));
+ pointcutMap.put(expression, def);
+ }
+
+ MapBasedMethodDefinitionSource mapBasedMethodDefinitionSource = new MapBasedMethodDefinitionSource();
+
+ // Now create and populate our ProtectPointcutBeanPostProcessor, if needed
+ if (pointcutMap.size() > 0) {
+ RootBeanDefinition ppbp = new RootBeanDefinition(ProtectPointcutPostProcessor.class);
+ ppbp.setRole(BeanDefinition.ROLE_INFRASTRUCTURE);
+ ppbp.getConstructorArgumentValues().addGenericArgumentValue(mapBasedMethodDefinitionSource);
+ ppbp.getPropertyValues().addPropertyValue("pointcutMap", pointcutMap);
+ parserContext.getRegistry().registerBeanDefinition(BeanIds.PROTECT_POINTCUT_POST_PROCESSOR, ppbp);
+ }
+
+ // Create our list of method metadata delegates
+ List delegates = new ArrayList();
+ delegates.add(mapBasedMethodDefinitionSource);
+
+ if (useSecured) {
+ try {
+ delegates.add(BeanUtils.instantiateClass(ClassUtils.forName(SECURED_METHOD_DEFINITION_SOURCE_CLASS)));
+ } catch (ClassNotFoundException shouldNotHappen) {
+ throw new IllegalStateException(shouldNotHappen);
+ }
+ }
+
+ if (useJsr250) {
+ try {
+ delegates.add(BeanUtils.instantiateClass(ClassUtils.forName(JSR_250_SECURITY_METHOD_DEFINITION_SOURCE_CLASS)));
+ } catch (ClassNotFoundException shouldNotHappen) {
+ throw new IllegalStateException(shouldNotHappen);
+ }
+ }
+
+ // Register our DelegatingMethodDefinitionSource
+ RootBeanDefinition delegatingMethodDefinitionSource = new RootBeanDefinition(DelegatingMethodDefinitionSource.class);
+ delegatingMethodDefinitionSource.setRole(BeanDefinition.ROLE_INFRASTRUCTURE);
+ delegatingMethodDefinitionSource.getPropertyValues().addPropertyValue("methodDefinitionSources", delegates);
+ parserContext.getRegistry().registerBeanDefinition(BeanIds.DELEGATING_METHOD_DEFINITION_SOURCE, delegatingMethodDefinitionSource);
+
+ // Register the applicable AccessDecisionManager, handling the special JSR 250 voter if being used
+ String accessManagerId = element.getAttribute(ATT_ACCESS_MGR);
+
+ if (!StringUtils.hasText(accessManagerId)) {
+ ConfigUtils.registerDefaultAccessManagerIfNecessary(parserContext);
+
+ if (useJsr250) {
+ ConfigUtils.addVoter(new RootBeanDefinition(JSR_250_VOTER_CLASS, null, null), parserContext);
+ }
+
+ accessManagerId = BeanIds.ACCESS_MANAGER;
+ }
+
+ // MethodSecurityInterceptor
+ RootBeanDefinition interceptor = new RootBeanDefinition(MethodSecurityInterceptor.class);
+ interceptor.setRole(BeanDefinition.ROLE_INFRASTRUCTURE);
+
+ interceptor.getPropertyValues().addPropertyValue("accessDecisionManager", new RuntimeBeanReference(accessManagerId));
+ interceptor.getPropertyValues().addPropertyValue("authenticationManager", new RuntimeBeanReference(BeanIds.AUTHENTICATION_MANAGER));
+ interceptor.getPropertyValues().addPropertyValue("objectDefinitionSource", new RuntimeBeanReference(BeanIds.DELEGATING_METHOD_DEFINITION_SOURCE));
+ parserContext.getRegistry().registerBeanDefinition(BeanIds.METHOD_SECURITY_INTERCEPTOR, interceptor);
+
+ // MethodDefinitionSourceAdvisor
+ RootBeanDefinition advisor = new RootBeanDefinition(MethodDefinitionSourceAdvisor.class);
+ advisor.setRole(BeanDefinition.ROLE_INFRASTRUCTURE);
+ advisor.getConstructorArgumentValues().addGenericArgumentValue(interceptor);
+ parserContext.getRegistry().registerBeanDefinition(BeanIds.METHOD_DEFINITION_SOURCE_ADVISOR, advisor);
+
+ AopNamespaceUtils.registerAutoProxyCreatorIfNecessary(parserContext, element);
+
+ return null;
+ }
+}
diff --git a/core/src/main/java/org/springframework/security/config/SecurityNamespaceHandler.java b/core/src/main/java/org/springframework/security/config/SecurityNamespaceHandler.java
index ed60e3bfb0..6340320b28 100644
--- a/core/src/main/java/org/springframework/security/config/SecurityNamespaceHandler.java
+++ b/core/src/main/java/org/springframework/security/config/SecurityNamespaceHandler.java
@@ -21,7 +21,7 @@ public class SecurityNamespaceHandler extends NamespaceHandlerSupport {
registerBeanDefinitionParser(Elements.USER_SERVICE, new UserServiceBeanDefinitionParser());
registerBeanDefinitionParser(Elements.JDBC_USER_SERVICE, new JdbcUserServiceBeanDefinitionParser());
registerBeanDefinitionParser(Elements.AUTHENTICATION_PROVIDER, new AuthenticationProviderBeanDefinitionParser());
- registerBeanDefinitionParser(Elements.ANNOTATION_DRIVEN, new AnnotationDrivenBeanDefinitionParser());
+ registerBeanDefinitionParser(Elements.GLOBAL_METHOD_SECURITY, new GlobalMethodSecurityBeanDefinitionParser());
registerBeanDefinitionParser(Elements.AUTHENTICATION_MANAGER, new AuthenticationManagerBeanDefinitionParser());
registerBeanDefinitionParser(Elements.FILTER_INVOCATION_DEFINITION_SOURCE, new FilterInvocationDefinitionSourceBeanDefinitionParser());
diff --git a/core/src/main/java/org/springframework/security/intercept/method/DelegatingMethodDefinitionSource.java b/core/src/main/java/org/springframework/security/intercept/method/DelegatingMethodDefinitionSource.java
new file mode 100644
index 0000000000..e0372a5ee1
--- /dev/null
+++ b/core/src/main/java/org/springframework/security/intercept/method/DelegatingMethodDefinitionSource.java
@@ -0,0 +1,80 @@
+package org.springframework.security.intercept.method;
+
+import java.lang.reflect.Method;
+import java.util.Collection;
+import java.util.HashSet;
+import java.util.Iterator;
+import java.util.List;
+import java.util.Set;
+
+import org.springframework.beans.factory.InitializingBean;
+import org.springframework.security.ConfigAttributeDefinition;
+import org.springframework.util.Assert;
+
+/**
+ * Automatically tries a series of method definition sources, relying on the first source of metadata
+ * that provides a non-null response.
+ *
+ * @author Ben Alex
+ * @version $Id$
+ */
+public final class DelegatingMethodDefinitionSource implements MethodDefinitionSource, InitializingBean {
+ private List methodDefinitionSources;
+
+ public void afterPropertiesSet() throws Exception {
+ Assert.notEmpty(methodDefinitionSources, "A list of MethodDefinitionSources is required");
+ }
+
+ public ConfigAttributeDefinition getAttributes(Method method, Class targetClass) {
+ Iterator i = methodDefinitionSources.iterator();
+ while (i.hasNext()) {
+ MethodDefinitionSource s = (MethodDefinitionSource) i.next();
+ ConfigAttributeDefinition result = s.getAttributes(method, targetClass);
+ if (result != null) {
+ return result;
+ }
+ }
+ return null;
+ }
+
+ public ConfigAttributeDefinition getAttributes(Object object) throws IllegalArgumentException {
+ Iterator i = methodDefinitionSources.iterator();
+ while (i.hasNext()) {
+ MethodDefinitionSource s = (MethodDefinitionSource) i.next();
+ ConfigAttributeDefinition result = s.getAttributes(object);
+ if (result != null) {
+ return result;
+ }
+ }
+ return null;
+ }
+
+ public Collection getConfigAttributeDefinitions() {
+ Set set = new HashSet();
+ Iterator i = methodDefinitionSources.iterator();
+ while (i.hasNext()) {
+ MethodDefinitionSource s = (MethodDefinitionSource) i.next();
+ Collection attrs = s.getConfigAttributeDefinitions();
+ if (attrs != null) {
+ set.addAll(attrs);
+ }
+ }
+ return set;
+ }
+
+ public boolean supports(Class clazz) {
+ Iterator i = methodDefinitionSources.iterator();
+ while (i.hasNext()) {
+ MethodDefinitionSource s = (MethodDefinitionSource) i.next();
+ if (s.supports(clazz)) {
+ return true;
+ }
+ }
+ return false;
+ }
+
+ public void setMethodDefinitionSources(List methodDefinitionSources) {
+ Assert.notEmpty(methodDefinitionSources, "A list of MethodDefinitionSources is required");
+ this.methodDefinitionSources = methodDefinitionSources;
+ }
+}
diff --git a/core/src/main/java/org/springframework/security/intercept/method/ProtectPointcutPostProcessor.java b/core/src/main/java/org/springframework/security/intercept/method/ProtectPointcutPostProcessor.java
new file mode 100644
index 0000000000..c455f5b8ce
--- /dev/null
+++ b/core/src/main/java/org/springframework/security/intercept/method/ProtectPointcutPostProcessor.java
@@ -0,0 +1,153 @@
+package org.springframework.security.intercept.method;
+
+import java.lang.reflect.Method;
+import java.util.HashSet;
+import java.util.Iterator;
+import java.util.LinkedHashMap;
+import java.util.Map;
+import java.util.Set;
+
+import org.apache.commons.logging.Log;
+import org.apache.commons.logging.LogFactory;
+import org.aspectj.weaver.tools.PointcutExpression;
+import org.aspectj.weaver.tools.PointcutParser;
+import org.aspectj.weaver.tools.PointcutPrimitive;
+import org.springframework.beans.BeansException;
+import org.springframework.beans.factory.config.BeanPostProcessor;
+import org.springframework.security.ConfigAttributeDefinition;
+import org.springframework.security.intercept.method.aopalliance.MethodDefinitionSourceAdvisor;
+import org.springframework.util.Assert;
+
+/**
+ * Parses AspectJ pointcut expressions, registering methods that match the pointcut with a
+ * traditional {@link MapBasedMethodDefinitionSource}.
+ *
+ *
+ * This class provides a convenient way of declaring a list of pointcuts, and then
+ * having every method of every bean defined in the Spring application context compared with
+ * those pointcuts. Where a match is found, the matching method will be registered with the
+ * {@link MapBasedMethodDefinitionSource}.
+ *
+ *
+ *
+ * It is very important to understand that only the first pointcut that matches a given
+ * method will be taken as authoritative for that method. This is why pointcuts should be provided
+ * as a LinkedHashMap, because their order is very important.
+ *
+ *
+ *
+ * Note also that only beans defined in the Spring application context will be examined by this
+ * class.
+ *
+ *
+ *
+ * Because this class registers method security metadata with {@link MapBasedMethodDefinitionSource},
+ * normal Spring Security capabilities such as {@link MethodDefinitionSourceAdvisor} can be used.
+ * It does not matter the fact the method metadata was originally obtained from an AspectJ pointcut
+ * expression evaluation.
+ *
+ *
+ * @author Ben Alex
+ * @verion $Id$
+ *
+ */
+public final class ProtectPointcutPostProcessor implements BeanPostProcessor {
+
+ private static final Log logger = LogFactory.getLog(ProtectPointcutPostProcessor.class);
+
+ private Map pointcutMap = new LinkedHashMap(); /** Key: string-based pointcut, value: ConfigAttributeDefinition */
+ private MapBasedMethodDefinitionSource mapBasedMethodDefinitionSource;
+ private PointcutParser parser;
+
+ public ProtectPointcutPostProcessor(MapBasedMethodDefinitionSource mapBasedMethodDefinitionSource) {
+ Assert.notNull(mapBasedMethodDefinitionSource, "MapBasedMethodDefinitionSource to populate is required");
+ this.mapBasedMethodDefinitionSource = mapBasedMethodDefinitionSource;
+
+ // Setup AspectJ pointcut expression parser
+ Set supportedPrimitives = new HashSet();
+ supportedPrimitives.add(PointcutPrimitive.EXECUTION);
+ supportedPrimitives.add(PointcutPrimitive.ARGS);
+ supportedPrimitives.add(PointcutPrimitive.REFERENCE);
+// supportedPrimitives.add(PointcutPrimitive.THIS);
+// supportedPrimitives.add(PointcutPrimitive.TARGET);
+// supportedPrimitives.add(PointcutPrimitive.WITHIN);
+// supportedPrimitives.add(PointcutPrimitive.AT_ANNOTATION);
+// supportedPrimitives.add(PointcutPrimitive.AT_WITHIN);
+// supportedPrimitives.add(PointcutPrimitive.AT_ARGS);
+// supportedPrimitives.add(PointcutPrimitive.AT_TARGET);
+ parser = PointcutParser.getPointcutParserSupportingSpecifiedPrimitivesAndUsingContextClassloaderForResolution(supportedPrimitives);
+ }
+
+ public Object postProcessAfterInitialization(Object bean, String beanName) throws BeansException {
+ return bean;
+ }
+
+ public Object postProcessBeforeInitialization(Object bean, String beanName) throws BeansException {
+ // Obtain methods for the present bean
+ Method[] methods;
+ try {
+ methods = bean.getClass().getMethods();
+ } catch (Exception e) {
+ throw new IllegalStateException(e);
+ }
+
+ // Check to see if any of those methods are compatible with our pointcut expressions
+ for (int i = 0; i < methods.length; i++) {
+ Iterator iter = pointcutMap.keySet().iterator();
+ while (iter.hasNext()) {
+ String ex = iter.next().toString();
+
+ // Parse the presented AspectJ pointcut expression
+ PointcutExpression expression = parser.parsePointcutExpression(ex);
+
+ // Try for the bean class directly
+ if (attemptMatch(bean.getClass(), methods[i], expression, beanName)) {
+ // We've found the first expression that matches this method, so move onto the next method now
+ break; // the "while" loop, not the "for" loop
+ }
+ }
+ }
+
+ return bean;
+ }
+
+ private boolean attemptMatch(Class targetClass, Method method, PointcutExpression expression, String beanName) {
+ // Determine if the presented AspectJ pointcut expression matches this method
+ boolean matches = expression.matchesMethodExecution(method).alwaysMatches();
+
+ // Handle accordingly
+ if (matches) {
+ ConfigAttributeDefinition attr = (ConfigAttributeDefinition) pointcutMap.get(expression.getPointcutExpression());
+
+ if (logger.isDebugEnabled()) {
+ logger.debug("AspectJ pointcut expression '" + expression.getPointcutExpression() + "' matches target class '" + targetClass.getName() + "' (bean ID '" + beanName + "') for method '" + method + "'; registering security configuration attribute '" + attr + "'");
+ }
+
+ mapBasedMethodDefinitionSource.addSecureMethod(targetClass, method.getName(), attr);
+ }
+
+ return matches;
+ }
+
+ public void setPointcutMap(Map map) {
+ Assert.notEmpty(map);
+ Iterator i = map.keySet().iterator();
+ while (i.hasNext()) {
+ String expression = i.next().toString();
+ Object value = map.get(expression);
+ Assert.isInstanceOf(ConfigAttributeDefinition.class, value, "Map keys must be instances of ConfigAttributeDefinition");
+ addPointcut(expression, (ConfigAttributeDefinition) value);
+ }
+ }
+
+ public void addPointcut(String pointcutExpression, ConfigAttributeDefinition definition) {
+ Assert.hasText(pointcutExpression, "An AspecTJ pointcut expression is required");
+ Assert.notNull(definition, "ConfigAttributeDefinition required");
+ pointcutMap.put(pointcutExpression, definition);
+
+ if (logger.isDebugEnabled()) {
+ logger.debug("AspectJ pointcut expression '" + pointcutExpression + "' registered for security configuration attribute '" + definition + "'");
+ }
+ }
+
+}
diff --git a/core/src/main/resources/org/springframework/security/config/spring-security-2.0.rnc b/core/src/main/resources/org/springframework/security/config/spring-security-2.0.rnc
index 87f466a83f..f8a7b6f7ad 100644
--- a/core/src/main/resources/org/springframework/security/config/spring-security-2.0.rnc
+++ b/core/src/main/resources/org/springframework/security/config/spring-security-2.0.rnc
@@ -143,26 +143,41 @@ intercept-methods.attlist &=
protect =
- ## Defines a protected method and the access control configuration attributes that apply to it
+ ## 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".
element protect {protect.attlist, empty}
protect.attlist &=
## A method name
attribute method {xsd:string}
protect.attlist &=
- ## Access configuration attributes list that applies to the method, e.g. "ROLE_A,ROLE_B"
+ ## Access configuration attributes list that applies to the method, e.g. "ROLE_A,ROLE_B".
attribute access {xsd:string}
-annotation-driven =
- ## Activates security annotation scanning. All beans registered in the Spring application context will be scanned for Spring Security annotations. Where found, the beans will automatically be proxied and security authorization applied to the methods accordingly. Please ensure you have the spring-security-tiger-XXX.jar on your classpath.
- element annotation-driven {annotation-driven.attlist}
-annotation-driven.attlist &=
- ## Specifies that JSR-250 style attributes are to be used (for example "RolesAllowed" instead of "Secured"). This will require the javax.annotation.security classes on the classpath. Defaults to false.
- attribute jsr250 {"true" | "false" }?
-annotation-driven.attlist &=
+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" }?
+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" }?
+global-method-security.attlist &=
## Optional AccessDecisionManager bean ID to override the default.
attribute access-decision-manager-ref {xsd:string}?
+
+protect-pointcut =
+ ## 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.
+ element protect-pointcut {protect-pointcut.attlist, empty}
+protect-pointcut.attlist &=
+ ## An AspectJ expression, including the 'execution' keyword. For example, 'execution(int com.foo.TargetObject.countLength(String))' (without the quotes).
+ attribute expression {xsd:string}
+protect-pointcut.attlist &=
+ ## Access configuration attributes list that applies to all methods matching the pointcut, e.g. "ROLE_A,ROLE_B"
+ attribute access {xsd:string}
+
+
http =
## Container element for HTTP security configuration
element http {http.attlist, (intercept-url+ & form-login? & openid-login & x509? & http-basic? & logout? & concurrent-session-control? & remember-me? & anonymous? & port-mappings) }
diff --git a/core/src/main/resources/org/springframework/security/config/spring-security-2.0.xsd b/core/src/main/resources/org/springframework/security/config/spring-security-2.0.xsd
index 17a34c16b9..80a8e93e77 100644
--- a/core/src/main/resources/org/springframework/security/config/spring-security-2.0.xsd
+++ b/core/src/main/resources/org/springframework/security/config/spring-security-2.0.xsd
@@ -1,1832 +1,995 @@
-
-
-
-
-
-
-
-
-
- Defines the hashing algorithm used on user passwords. We recommend strongly against using MD4, as it is a very weak hashing algorithm.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Whether a string should be base64 encoded
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Specifies an IP port number. Used to configure an embedded LDAP server, for example.
-
-
-
-
-
-
-
-
-
-
-
-
-
- Specifies a URL.
-
-
-
-
-
-
-
-
-
-
-
-
-
- A bean identifier, used for referring to the bean elsewhere in the context.
-
-
-
-
-
-
-
-
-
-
-
-
-
- Defines a reference to a Spring bean Id.
-
-
-
-
-
-
-
-
-
-
-
-
-
- A reference to a user-service (or UserDetailsService bean) Id
-
-
-
-
-
-
-
-
+
+
+
+
-
- element which defines a password encoding strategy. Used by an authentication provider to convert submitted passwords to hashed versions, for example.
-
+ Defines the hashing algorithm used on user passwords. We recommend strongly against using MD4, as it is a very weak hashing algorithm.
-
-
-
-
-
-
-
-
-
-
-
- A property of the UserDetails object which will be used as salt by a password encoder. Typically something like "username" might be used.
-
-
-
-
-
-
-
-
-
- A single value that will be used as the salt for a password encoder.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Defines a reference to a Spring bean Id.
-
-
-
-
-
-
-
-
-
- Defines the hashing algorithm used on user passwords. We recommend strongly against using MD4, as it is a very weak hashing algorithm.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Whether a string should be base64 encoded
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- A property of the UserDetails object which will be used as salt by a password encoder. Typically something like "username" might be used.
-
-
-
-
-
-
-
-
-
-
-
-
-
- A single value that will be used as the salt for a password encoder.
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
+
+
+
+
-
- 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.
-
+ Whether a string should be base64 encoded
-
-
-
-
-
-
-
-
-
-
-
-
-
- A bean identifier, used for referring to the bean elsewhere in the context.
-
-
-
-
-
-
-
-
-
- Specifies a URL.
-
-
-
-
-
-
-
-
-
- Specifies an IP port number. Used to configure an embedded LDAP server, for example.
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
-
-
- Explicitly specifies an ldif file resource to load into an embedded LDAP server
-
-
-
-
-
-
-
-
-
- Optional root suffix for the embedded LDAP server. Default is "dc=springframework,dc=org"
-
-
-
-
-
-
-
-
-
-
-
-
-
- The optional server to use. If omitted, and a default LDAP server is registered (using <ldap-server> with no Id), that server will be used.
-
-
-
-
-
-
-
-
-
-
-
-
-
- Group search filter. Defaults to (uniqueMember={0}). The substituted parameter is the DN of the user.
-
-
-
-
-
-
-
-
-
-
-
-
-
- Search base for group membership searches. Defaults to "ou=groups".
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Search base for user searches. Defaults to "".
-
-
-
-
-
-
-
-
-
-
-
-
-
- The LDAP attribute name which contains the role name which will be used within Spring Security. Defaults to "cn".
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- A bean identifier, used for referring to the bean elsewhere in the context.
-
-
-
-
-
-
-
-
-
- The optional server to use. If omitted, and a default LDAP server is registered (using <ldap-server> with no Id), that server will be used.
-
-
-
-
-
-
-
-
-
-
-
-
-
- Group search filter. Defaults to (uniqueMember={0}). The substituted parameter is the DN of the user.
-
-
-
-
-
-
-
-
-
- Search base for group membership searches. Defaults to "ou=groups".
-
-
-
-
-
-
-
-
-
- The LDAP attribute name which contains the role name which will be used within Spring Security. Defaults to "cn".
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
-
- Sets up an ldap authentication provider
-
+ 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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- The optional server to use. If omitted, and a default LDAP server is registered (using <ldap-server> with no Id), that server will be used.
-
-
-
-
-
-
-
-
-
-
-
-
-
- Search base for group membership searches. Defaults to "ou=groups".
-
-
-
-
-
-
-
-
-
- Group search filter. Defaults to (uniqueMember={0}). The substituted parameter is the DN of the user.
-
-
-
-
-
-
-
-
-
- The LDAP attribute name which contains the role name which will be used within Spring Security. Defaults to "cn".
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
+
+
+
+
+
+
+
+
+
+
-
- Specifies that an LDAP provider should use an LDAP compare operation of the user's password to authenticate the user
-
+ Specifies an IP port number. Used to configure an embedded LDAP server, for example.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- The attribute in the directory which contains the user password. Defaults to "userPassword".
-
-
-
-
-
-
-
-
-
- Defines the hashing algorithm used on user passwords. We recommend strongly against using MD4, as it is a very weak hashing algorithm.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
-
- 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
-
+ Specifies a URL.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Optional AccessDecisionManager bean ID to be used by the created method security interceptor.
-
-
-
-
-
-
-
-
+
+
+
+
-
- Defines a protected method and the access control configuration attributes that apply to it
-
+ A bean identifier, used for referring to the bean elsewhere in the context.
-
-
-
-
-
-
-
-
-
-
-
-
-
- A method name
-
-
-
-
-
-
-
-
-
- Access configuration attributes list that applies to the method, e.g. "ROLE_A,ROLE_B"
-
-
-
-
-
-
-
-
+
+
+
+
-
- Activates security annotation scanning. All beans registered in the Spring application context will be scanned for Spring Security annotations. Where found, the beans will automatically be proxied and security authorization applied to the methods accordingly. Please ensure you have the spring-security-tiger-XXX.jar on your classpath.
-
+ Defines a reference to a Spring bean Id.
-
-
-
-
-
-
-
-
-
-
-
-
-
- Specifies that JSR-250 style attributes are to be used (for example "RolesAllowed" instead of "Secured"). This will require the javax.annotation.security classes on the classpath. Defaults to false.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Optional AccessDecisionManager bean ID to override the default.
-
-
-
-
-
-
-
-
+
+
+
+
-
- Container element for HTTP security configuration
-
+ A reference to a user-service (or UserDetailsService bean) Id
-
-
-
-
-
-
-
- Specifies the access attributes and/or filter list for a particular set of URLs.
-
-
-
-
-
-
-
-
-
-
-
-
- Sets up a form login configuration for authentication with a username and password
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Adds support for X.509 client authentication.
-
-
-
-
-
-
-
-
-
-
-
-
- Adds support for basic authentication (this is an element to permit future expansion, such as supporting an "ignoreFailure" attribute)
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
-
-
-
- Adds support for concurrent session control, allowing limits to be placed on the number of sessions a user can have.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Adds support for automatically granting all anonymous web requests a particular principal identity and a corresponding granted authority.
-
-
-
-
-
-
-
-
-
-
-
-
- Defines the list of mappings between http and https ports for use in redirects
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 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".
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Controls the eagerness with which an HTTP session is created. If not set, defaults to "ifRequired".
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Whether test URLs should be converted to lower case prior to comparing with defined path patterns. If unspecified, defaults to "true".
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Provides versions of HttpServletRequest security methods such as isUserInRole() and getPrincipal() which are implemented by accessing the Spring SecurityContext. Defaults to "true".
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Optional attribute specifying the ID of the AccessDecisionManager implementation which should be used for authorizing HTTP requests.
-
-
-
-
-
-
-
-
-
- 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".
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
- The access configuration attributes that apply for the configured path.
-
-
-
-
-
-
-
-
-
- The HTTP Method for which the access configuration attributes should apply. If not specified, the attributes will apply to any method.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 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).
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Used to specify that a URL must be accessed over http or https
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
- Specifies the URL to display once the user has logged out. If not specified, defaults to /.
-
-
-
-
-
-
-
-
-
- Specifies whether a logout also causes HttpSession invalidation, which is generally desirable. If unspecified, defaults to true.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- The URL that the login form is posted to. If unspecified, it defaults to /j_spring_security_check.
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
-
- Sets up form login for authentication with an Open ID identity
-
-
-
-
-
-
-
-
-
-
- A reference to a user-service (or UserDetailsService bean) Id
-
-
-
-
-
-
-
-
-
-
-
- Used to explicitly configure a FilterChainProxy instance with a FilterChainMap
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 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 <http> element. The intercept-url elements used should only contain pattern, method and access attributes. Any others will result in a configuration error.
-
-
-
-
-
-
-
-
-
- Specifies the access attributes and/or filter list for a particular set of URLs.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- A bean identifier, used for referring to the bean elsewhere in the context.
-
-
-
-
-
-
-
-
-
- as for http element
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- The key used between the provider and filter. This generally does not need to be set. If unset, it will default to "doesNotMatter".
-
-
-
-
-
-
-
-
-
- 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".
-
-
-
-
-
-
-
-
-
- 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".
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- The regular expression used to obtain the username from the certificate's subject. Defaults to matching on the common name using the pattern "CN=(.*?),".
-
-
-
-
-
-
-
-
-
- A reference to a user-service (or UserDetailsService bean) Id
-
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
-
-
-
-
- The alias you wish to use for the AuthenticationManager bean
-
-
-
-
-
-
-
-
-
-
- Indicates that the contained user-service should be used as an authentication source.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- A reference to a user-service (or UserDetailsService bean) Id
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Creates an in-memory UserDetailsService from a properties file or a list of "user" child elements.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- A bean identifier, used for referring to the bean elsewhere in the context.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Represents a user in the application.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- The username assigned to the user.
-
-
-
-
-
-
-
-
-
- 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).
-
-
-
-
-
-
-
-
-
- One of more authorities granted to the user. Separate authorities with a comma (but no space). For example, "ROLE_USER,ROLE_ADMINISTRATOR"
-
-
-
-
-
-
-
-
-
- Can be set to "true" to mark an account as locked and unusable.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- Causes creation of a JDBC-based UserDetailsService.
-
-
-
-
-
-
-
-
- A bean identifier, used for referring to the bean elsewhere in the context.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- The bean ID of the DataSource which provides the required tables.
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+ element which defines a password encoding strategy. Used by an authentication provider to convert submitted passwords to hashed versions, for example.
+
+
-
-
-
+
-
-
-
-
+
+
+
+
+
-
- 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.
-
+ Defines a reference to a Spring bean Id.
-
-
-
-
-
-
- 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.
-
-
-
-
-
-
-
-
-
- The filter immediately before which the custom-filter should be placed in the chain
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- 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.
-
-
-
+
+
+
+ Defines the hashing algorithm used on user passwords. We recommend strongly against using MD4, as it is a very weak hashing algorithm.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Whether a string should be base64 encoded
+
+
+
+
+
+
+
+
+
+
+
+
+
+ A property of the UserDetails object which will be used as salt by a password encoder. Typically something like "username" might be used.
+
-
-
-
-
-
-
-
-
-
- The filter immediately before which the custom-filter should be placed in the chain
-
-
-
+
+
+ A single value that will be used as the salt for a password encoder.
+
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
+
+
+
+
+
+ A property of the UserDetails object which will be used as salt by a password encoder. Typically something like "username" might be used.
+
+
+
+
+
+
+ A single value that will be used as the salt for a password encoder.
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+ A bean identifier, used for referring to the bean elsewhere in the context.
+
+
+
+
+ Specifies a URL.
+
+
+
+
+ Specifies an IP port number. Used to configure an embedded LDAP server, for example.
+
+
+
+
+ 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.
+
+
+
+
+
+ Explicitly specifies an ldif file resource to load into an embedded LDAP server
+
+
+
+
+ Optional root suffix for the embedded LDAP server. Default is "dc=springframework,dc=org"
+
+
+
+
+
+
+ The optional server to use. If omitted, and a default LDAP server is registered (using <ldap-server> with no Id), that server will be used.
+
+
+
+
+
+
+ Group search filter. Defaults to (uniqueMember={0}). The substituted parameter is the DN of the user.
+
+
+
+
+
+
+ Search base for group membership searches. Defaults to "ou=groups".
+
+
+
+
+
+
+
+
+
+ Search base for user searches. Defaults to "".
+
+
+
+
+
+
+ The LDAP attribute name which contains the role name which will be used within Spring Security. Defaults to "cn".
+
+
+
+
+
+
+
+
+
+
+
+ A bean identifier, used for referring to the bean elsewhere in the context.
+
+
+
+
+ The optional server to use. If omitted, and a default LDAP server is registered (using <ldap-server> with no Id), that server will be used.
+
+
+
+
+
+
+ Group search filter. Defaults to (uniqueMember={0}). The substituted parameter is the DN of the user.
+
+
+
+
+ Search base for group membership searches. Defaults to "ou=groups".
+
+
+
+
+ The LDAP attribute name which contains the role name which will be used within Spring Security. Defaults to "cn".
+
+
+
+
+
+ Sets up an ldap authentication provider
+
+
+
+
+
+
+
+
+
+
+
+ The optional server to use. If omitted, and a default LDAP server is registered (using <ldap-server> with no Id), that server will be used.
+
+
+
+
+
+
+ Search base for group membership searches. Defaults to "ou=groups".
+
+
+
+
+ Group search filter. Defaults to (uniqueMember={0}). The substituted parameter is the DN of the user.
+
+
+
+
+ The LDAP attribute name which contains the role name which will be used within Spring Security. Defaults to "cn".
+
+
+
+
+ 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.
+
+
+
+
+
+ Specifies that an LDAP provider should use an LDAP compare operation of the user's password to authenticate the user
+
+
+
+
+
+
+
+
+
+
+
+ The attribute in the directory which contains the user password. Defaults to "userPassword".
+
+
+
+
+ Defines the hashing algorithm used on user passwords. We recommend strongly against using MD4, as it is a very weak hashing algorithm.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 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
+
+
+
+
+
+
+
+
+
+
+
+ Optional AccessDecisionManager bean ID to be used by the created method security interceptor.
+
+
+
+
+
+ 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".
+
+
+
+
+
+
+
+
+ A method name
+
+
+
+
+ Access configuration attributes list that applies to the method, e.g. "ROLE_A,ROLE_B".
+
+
+
+
+
+ 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).
+
+
+
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+
+
+ Optional AccessDecisionManager bean ID to override the default.
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+ An AspectJ expression, including the 'execution' keyword. For example, 'execution(int com.foo.TargetObject.countLength(String))' (without the quotes).
+
+
+
+
+ Access configuration attributes list that applies to all methods matching the pointcut, e.g. "ROLE_A,ROLE_B"
+
+
+
+
+
+ Container element for HTTP security configuration
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 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".
+
+
+
+
+
+
+
+
+
+
+ Controls the eagerness with which an HTTP session is created. If not set, defaults to "ifRequired".
+
+
+
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+
+
+ Whether test URLs should be converted to lower case prior to comparing with defined path patterns. If unspecified, defaults to "true".
+
+
+
+
+
+
+
+
+
+
+ Provides versions of HttpServletRequest security methods such as isUserInRole() and getPrincipal() which are implemented by accessing the Spring SecurityContext. Defaults to "true".
+
+
+
+
+
+
+
+
+
+
+ Optional attribute specifying the ID of the AccessDecisionManager implementation which should be used for authorizing HTTP requests.
+
+
+
+
+ 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".
+
+
+
+
+
+ Specifies the access attributes and/or filter list for a particular set of URLs.
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+ The access configuration attributes that apply for the configured path.
+
+
+
+
+ The HTTP Method for which the access configuration attributes should apply. If not specified, the attributes will apply to any method.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 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).
+
+
+
+
+
+
+
+
+
+ Used to specify that a URL must be accessed over http or https
+
+
+
+
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+ Specifies the URL to display once the user has logged out. If not specified, defaults to /.
+
+
+
+
+ Specifies whether a logout also causes HttpSession invalidation, which is generally desirable. If unspecified, defaults to true.
+
+
+
+
+
+
+
+
+
+
+
+ Sets up a form login configuration for authentication with a username and password
+
+
+
+
+
+
+
+
+ The URL that the login form is posted to. If unspecified, it defaults to /j_spring_security_check.
+
+
+
+
+ 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.
+
+
+
+
+ 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.
+
+
+
+
+ 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.
+
+
+
+
+
+ Sets up form login for authentication with an Open ID identity
+
+
+
+
+
+ A reference to a user-service (or UserDetailsService bean) Id
+
+
+
+
+
+
+ Used to explicitly configure a FilterChainProxy instance with a FilterChainMap
+
+
+
+
+
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+
+
+
+ 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 <http> element. The intercept-url elements used should only contain pattern, method and access attributes. Any others will result in a configuration error.
+
+
+
+
+
+
+
+
+
+
+
+ A bean identifier, used for referring to the bean elsewhere in the context.
+
+
+
+
+ as for http element
+
+
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+
+
+
+
+ Adds support for basic authentication (this is an element to permit future expansion, such as supporting an "ignoreFailure" attribute)
+
+
+
+
+
+ Adds support for concurrent session control, allowing limits to be placed on the number of sessions a user can have.
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Adds support for automatically granting all anonymous web requests a particular principal identity and a corresponding granted authority.
+
+
+
+
+
+
+
+
+ The key used between the provider and filter. This generally does not need to be set. If unset, it will default to "doesNotMatter".
+
+
+
+
+ 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".
+
+
+
+
+ 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".
+
+
+
+
+
+ Defines the list of mappings between http and https ports for use in redirects
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+ Adds support for X.509 client authentication.
+
+
+
+
+
+
+
+
+ The regular expression used to obtain the username from the certificate's subject. Defaults to matching on the common name using the pattern "CN=(.*?),".
+
+
+
+
+ A reference to a user-service (or UserDetailsService bean) Id
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+
+ The alias you wish to use for the AuthenticationManager bean
+
+
+
+
+
+ Indicates that the contained user-service should be used as an authentication source.
+
+
+
+
+
+
+
+
+
+
+
+
+ A reference to a user-service (or UserDetailsService bean) Id
+
+
+
+
+
+
+
+
+ Creates an in-memory UserDetailsService from a properties file or a list of "user" child elements.
+
+
+
+
+
+
+
+ A bean identifier, used for referring to the bean elsewhere in the context.
+
+
+
+
+
+
+
+
+
+
+ Represents a user in the application.
+
+
+
+
+
+
+
+
+ The username assigned to the user.
+
+
+
+
+ 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).
+
+
+
+
+ One of more authorities granted to the user. Separate authorities with a comma (but no space). For example, "ROLE_USER,ROLE_ADMINISTRATOR"
+
+
+
+
+ Can be set to "true" to mark an account as locked and unusable.
+
+
+
+
+
+
+
+
+
+
+
+ Causes creation of a JDBC-based UserDetailsService.
+
+
+
+
+ A bean identifier, used for referring to the bean elsewhere in the context.
+
+
+
+
+
+
+
+
+ The bean ID of the DataSource which provides the required tables.
+
+
+
+
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+ 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.
+
+
+
+
+ The filter immediately before which the custom-filter should be placed in the chain
+
+
+
+
+
+
+
+ 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.
+
+
+
+
+
+
+ The filter immediately before which the custom-filter should be placed in the chain
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
diff --git a/core/src/main/resources/org/springframework/security/config/spring-security.xsl b/core/src/main/resources/org/springframework/security/config/spring-security.xsl
index 98ccb27fcf..d6f0b7c7be 100644
--- a/core/src/main/resources/org/springframework/security/config/spring-security.xsl
+++ b/core/src/main/resources/org/springframework/security/config/spring-security.xsl
@@ -10,7 +10,7 @@
- ,intercept-url,form-login,x509,http-basic,logout,concurrent-session-control,remember-me,anonymous,port-mappings,password-compare-element,salt-source,filter-chain,
+ ,intercept-url,form-login,x509,http-basic,logout,concurrent-session-control,remember-me,anonymous,port-mappings,password-compare-element,salt-source,filter-chain,protect-pointcut,
diff --git a/pom.xml b/pom.xml
index 22d3b14752..e9aeb86100 100644
--- a/pom.xml
+++ b/pom.xml
@@ -662,7 +662,6 @@
org.aspectj
aspectjweaver
- test
true
1.5.4
diff --git a/samples/pom.xml b/samples/pom.xml
index 1eea3aa53d..464dc74413 100644
--- a/samples/pom.xml
+++ b/samples/pom.xml
@@ -29,6 +29,11 @@
aspectj
aspectjrt