namespace a = "http://relaxng.org/ns/compatibility/annotations/1.0"
datatypes xsd = "http://www.w3.org/2001/XMLSchema-datatypes"

default namespace = "http://www.springframework.org/schema/security"

start = http | ldap-server | authentication-provider | ldap-authentication-provider | any-user-service | ldap-server | ldap-authentication-provider

hash =
    ## Defines the hashing algorithm used on user passwords. We recommend strongly against using MD4, as it is a very weak hashing algorithm.
    attribute hash {"plaintext" | "sha" | "sha-256" | "md5" | "md4" | "{sha}" | "{ssha}"}
base64 =
    ## Whether a string should be base64 encoded
    attribute base64 {xsd:boolean}
request-matcher =
    ## Supersedes the 'path-type' attribute. Defines the strategy use for matching incoming requests. Currently the options are 'ant' (for ant path patterns), 'regex' for regular expressions and 'ciRegex' for case-insensitive regular expressions.
    attribute request-matcher {"ant" | "regex" | "ciRegex"}
path-type =
    ## Deprecated. Use request-matcher instead.
    attribute path-type {"ant" | "regex"}
port =
    ## Specifies an IP port number. Used to configure an embedded LDAP server, for example.
    attribute port { xsd:positiveInteger }
url =
    ## Specifies a URL.
    attribute url { xsd:token }
id =
    ## A bean identifier, used for referring to the bean elsewhere in the context.
    attribute id {xsd:token}
name =
    ## A bean identifier, used for referring to the bean elsewhere in the context.
    attribute name {xsd:token}
ref =
    ## Defines a reference to a Spring bean Id.
    attribute ref {xsd:token}

cache-ref =
    ## Defines a reference to a cache for use with a UserDetailsService.
    attribute cache-ref {xsd:token}

user-service-ref =
    ## A reference to a user-service (or UserDetailsService bean) Id
    attribute user-service-ref {xsd:token}

authentication-manager-ref =
    ## A reference to an AuthenticationManager bean
    attribute authentication-manager-ref {xsd:token}

data-source-ref =
    ## A reference to a DataSource bean
    attribute data-source-ref {xsd:token}



debug =
    ## Enables Spring Security debugging infrastructure. This will provide human-readable (multi-line) debugging information to monitor requests coming into the security filters. This may include sensitive information, such as request parameters or headers, and should only be used in a development environment.
    element debug {empty}

password-encoder =
    ## element which defines a password encoding strategy. Used by an authentication provider to convert submitted passwords to hashed versions, for example.
    element password-encoder {password-encoder.attlist, salt-source?}
password-encoder.attlist &=
    ref | (hash? & base64?)

salt-source =
    ## Password salting strategy. A system-wide constant or a property from the UserDetails object can be used.
    element salt-source {user-property | system-wide | ref}
user-property =
    ## A property of the UserDetails object which will be used as salt by a password encoder. Typically something like "username" might be used.
    attribute user-property {xsd:token}
system-wide =
    ## A single value that will be used as the salt for a password encoder.
    attribute system-wide {xsd:token}

role-prefix =
    ## A non-empty string prefix that will be added to role strings loaded from persistent storage (e.g. "ROLE_"). Use the value "none" for no prefix in cases where the default is non-empty.
    attribute role-prefix {xsd:token}

use-expressions =
    ## Enables the use of expressions in the 'access' attributes in <intercept-url> elements rather than the traditional list of configuration attributes. Defaults to 'false'. If enabled, each attribute should contain a single boolean expression. If the expression evaluates to 'true', access will be granted.
    attribute use-expressions {xsd:boolean}

ldap-server =
    ## 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.
    element ldap-server {ldap-server.attlist}
ldap-server.attlist &= id?
ldap-server.attlist &= (url | port)?
ldap-server.attlist &=
    ## 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.
    attribute manager-dn {xsd:string}?
ldap-server.attlist &=
    ## The password for the manager DN. This is required if the manager-dn is specified.
    attribute manager-password {xsd:string}?
ldap-server.attlist &=
    ## Explicitly specifies an ldif file resource to load into an embedded LDAP server. The default is classpath*:*.ldiff
    attribute ldif { xsd:string }?
ldap-server.attlist &=
    ## Optional root suffix for the embedded LDAP server. Default is "dc=springframework,dc=org"
    attribute root { xsd:string }?

ldap-server-ref-attribute =
    ## 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.
    attribute server-ref {xsd:token}


group-search-filter-attribute =
    ## Group search filter. Defaults to (uniqueMember={0}). The substituted parameter is the DN of the user.
    attribute group-search-filter {xsd:token}
group-search-base-attribute =
    ## Search base for group membership searches. Defaults to "" (searching from the root).
    attribute group-search-base {xsd:token}
user-search-filter-attribute =
    ## The LDAP filter used to search for users (optional). For example "(uid={0})". The substituted parameter is the user's login name.
    attribute user-search-filter {xsd:token}
user-search-base-attribute =
    ## Search base for user searches. Defaults to "". Only used with a 'user-search-filter'.
    attribute user-search-base {xsd:token}
group-role-attribute-attribute =
    ## The LDAP attribute name which contains the role name which will be used within Spring Security. Defaults to "cn".
    attribute group-role-attribute {xsd:token}
user-details-class-attribute =
    ## Allows the objectClass of the user entry to be specified. If set, the framework will attempt to load standard attributes for the defined class into the returned UserDetails object
    attribute user-details-class {"person" | "inetOrgPerson"}
user-context-mapper-attribute =
    ## Allows explicit customization of the loaded user object by specifying a UserDetailsContextMapper bean which will be called with the context information from the user's directory entry
    attribute user-context-mapper-ref {xsd:token}


ldap-user-service =
    ## This element configures a LdapUserDetailsService which is a combination of a FilterBasedLdapUserSearch and a DefaultLdapAuthoritiesPopulator.
    element ldap-user-service {ldap-us.attlist}
ldap-us.attlist &= id?
ldap-us.attlist &=
    ldap-server-ref-attribute?
ldap-us.attlist &=
    user-search-filter-attribute?
ldap-us.attlist &=
    user-search-base-attribute?
ldap-us.attlist &=
    group-search-filter-attribute?
ldap-us.attlist &=
    group-search-base-attribute?
ldap-us.attlist &=
    group-role-attribute-attribute?
ldap-us.attlist &=
    cache-ref?
ldap-us.attlist &=
    role-prefix?
ldap-us.attlist &=
    (user-details-class-attribute | user-context-mapper-attribute)?

ldap-authentication-provider =
    ## Sets up an ldap authentication provider
    element ldap-authentication-provider {ldap-ap.attlist, password-compare-element?}
ldap-ap.attlist &=
    ldap-server-ref-attribute?
ldap-ap.attlist &=
    user-search-base-attribute?
ldap-ap.attlist &=
    user-search-filter-attribute?
ldap-ap.attlist &=
    group-search-base-attribute?
ldap-ap.attlist &=
    group-search-filter-attribute?
ldap-ap.attlist &=
    group-role-attribute-attribute?
ldap-ap.attlist &=
    ## 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.
    attribute user-dn-pattern {xsd:token}?
ldap-ap.attlist &=
    role-prefix?
ldap-ap.attlist &=
    (user-details-class-attribute | user-context-mapper-attribute)?

password-compare-element =
    ## Specifies that an LDAP provider should use an LDAP compare operation of the user's password to authenticate the user
    element password-compare {password-compare.attlist, password-encoder?}

password-compare.attlist &=
    ## The attribute in the directory which contains the user password. Defaults to "userPassword".
    attribute password-attribute {xsd:token}?
password-compare.attlist &=
    hash?

intercept-methods =
    ## 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
    element intercept-methods {intercept-methods.attlist, protect+}
intercept-methods.attlist &=
    ## Optional AccessDecisionManager bean ID to be used by the created method security interceptor.
    attribute access-decision-manager-ref {xsd:token}?


protect =
    ## 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:token}
protect.attlist &=
    ## Access configuration attributes list that applies to the method, e.g. "ROLE_A,ROLE_B".
    attribute access {xsd:token}

method-security-metadata-source =
    ## Creates a MethodSecurityMetadataSource instance
    element method-security-metadata-source {msmds.attlist, protect+}
msmds.attlist &= id?

msmds.attlist &= use-expressions?

global-method-security =
    ## Provides method security for all beans registered in the Spring application context. Specifically, beans will be scanned for matches with the ordered list of "protect-pointcut" sub-elements, Spring Security annotations and/or. 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 four sources of method security metadata (ie "protect-pointcut" declarations, expression annotations, @Secured and also JSR250 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 in annotations. If using annotations, the order of precedence is EL-based (@PreAuthorize etc.), @Secured and finally JSR-250.
    element global-method-security {global-method-security.attlist, (pre-post-annotation-handling | expression-handler)?, protect-pointcut*, after-invocation-provider*}
global-method-security.attlist &=
    ## Specifies whether the use of Spring Security's pre and post invocation annotations (@PreFilter, @PreAuthorize, @PostFilter, @PostAuthorize) should be enabled for this application context. Defaults to "disabled".
    attribute pre-post-annotations {"disabled" | "enabled" }?
global-method-security.attlist &=
    ## Specifies whether the use of Spring Security's @Secured annotations should be enabled for this application context. Defaults to "disabled".
    attribute secured-annotations {"disabled" | "enabled" }?
global-method-security.attlist &=
    ## 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 used for method security.
    attribute access-decision-manager-ref {xsd:token}?
global-method-security.attlist &=
    ## Optional RunAsmanager implementation which will be used by the configured MethodSecurityInterceptor
    attribute run-as-manager-ref {xsd:token}?
global-method-security.attlist &=
    ## Allows the advice "order" to be set for the method security interceptor.
    attribute order {xsd:token}?
global-method-security.attlist &=
    ## If true, class based proxying will be used instead of interface based proxying.
    attribute proxy-target-class {xsd:boolean}?
global-method-security.attlist &=
    ## Can be used to specify that AspectJ should be used instead of the default Spring AOP. If set, secured classes must be woven with the AnnotationSecurityAspect from the spring-security-aspects module.
    attribute mode {"aspectj"}?
global-method-security.attlist &=
    ## An external MethodSecurityMetadataSource instance can be supplied which will take priority over other sources (such as the default annotations).
    attribute metadata-source-ref {xsd:token}?
global-method-security.attlist &=
    authentication-manager-ref?


after-invocation-provider =
    ## Allows addition of extra AfterInvocationProvider beans which should be called by the MethodSecurityInterceptor created by global-method-security.
    element after-invocation-provider {ref}

pre-post-annotation-handling =
    ## Allows the default expression-based mechanism for handling Spring Security's pre and post invocation annotations (@PreFilter, @PreAuthorize, @PostFilter, @PostAuthorize) to be replace entirely. Only applies if these annotations are enabled.
    element pre-post-annotation-handling {invocation-attribute-factory, pre-invocation-advice, post-invocation-advice}

invocation-attribute-factory =
    ## Defines the PrePostInvocationAttributeFactory instance which is used to generate pre and post invocation metadata from the annotated methods.
    element invocation-attribute-factory {ref}

pre-invocation-advice =
    ## Customizes the PreInvocationAuthorizationAdviceVoter with the ref as the PreInvocationAuthorizationAdviceVoter for the <pre-post-annotation-handling> element.
    element pre-invocation-advice {ref}

post-invocation-advice =
    ## Customizes the PostInvocationAdviceProvider with the ref as the PostInvocationAuthorizationAdvice for the <pre-post-annotation-handling> element.
    element post-invocation-advice {ref}


expression-handler =
    ## Defines the SecurityExpressionHandler instance which will be used if expression-based access-control is enabled. A default implementation (with no ACL support) will be used if not supplied.
    element expression-handler {ref}

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:token}

http-firewall =
    ## Allows a custom instance of HttpFirewall to be injected into the FilterChainProxy created by the namespace.
    element http-firewall {ref}

http =
    ## Container element for HTTP security configuration. Multiple elements can now be defined, each with a specific pattern to which the enclosed security configuration applies. A pattern can also be configured to bypass Spring Security's filters completely by setting the "security" attribute to "none".
    element http {http.attlist, (intercept-url* & access-denied-handler? & form-login? & openid-login? & x509? & jee? & http-basic? & logout? & session-management & remember-me? & anonymous? & port-mappings & custom-filter* & request-cache? & expression-handler?) }
http.attlist &=
    ## The request URL pattern which will be mapped to the filter chain created by this <http> element. If omitted, the filter chain will match all requests.
    attribute pattern {xsd:token}?
http.attlist &=
    ## When set to 'none', requests matching the pattern attribute will be ignored by Spring Security. No security filters will be applied and no SecurityContext will be available. If set, the <http> element must be empty, with no children.
    attribute security {"none"}?
http.attlist &=
    ## Allows a RequestMatcher instance to be used, as an alternative to pattern-matching.
    attribute request-matcher-ref { xsd:token }?
http.attlist &=
    ## 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".
    attribute auto-config {xsd:boolean}?
http.attlist &=
    use-expressions?
http.attlist &=
    ## Controls the eagerness with which an HTTP session is created by Spring Security classes. If not set, defaults to "ifRequired". If "stateless" is used, this implies that the application guarantees that it will not create a session. This differs from the use of "never" which mans that Spring Security will not create a session, but will make use of one if the application does.
    attribute create-session {"ifRequired" | "always" | "never" | "stateless"}?
http.attlist &=
    ## A reference to a SecurityContextRepository bean. This can be used to customize how the SecurityContext is stored between requests.
    attribute security-context-repository-ref {xsd:token}?
http.attlist &=
    request-matcher?
http.attlist &=
    ## Deprecated. Use request-matcher instead.
    path-type?
http.attlist &=
    ## Provides versions of HttpServletRequest security methods such as isUserInRole() and getPrincipal() which are implemented by accessing the Spring SecurityContext. Defaults to "true".
    attribute servlet-api-provision {xsd:boolean}?
http.attlist &=
    ## If available, runs the request as the Subject acquired from the JaasAuthenticationToken. Defaults to "false".
    attribute jaas-api-provision {xsd:boolean}?
http.attlist &=
    ## Optional attribute specifying the ID of the AccessDecisionManager implementation which should be used for authorizing HTTP requests.
    attribute access-decision-manager-ref {xsd:token}?
http.attlist &=
    ## 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".
    attribute realm {xsd:token}?
http.attlist &=
    ## Allows a customized AuthenticationEntryPoint to be set on the ExceptionTranslationFilter.
    attribute entry-point-ref {xsd:token}?
http.attlist &=
    ## Corresponds to the observeOncePerRequest property of FilterSecurityInterceptor. Defaults to "true"
    attribute once-per-request {xsd:boolean}?
http.attlist &=
    ## Deprecated in favour of the access-denied-handler element.
    attribute access-denied-page {xsd:token}?
http.attlist &=
    ## Prevents the jsessionid parameter from being added to rendered URLs.
    attribute disable-url-rewriting {xsd:boolean}?
http.attlist &=
    ## Exposes the list of filters defined by this configuration under this bean name in the application context.
    name?
http.attlist &=
    authentication-manager-ref?

access-denied-handler =
    ## Defines the access-denied strategy that should be used. An access denied page can be defined or a reference to an AccessDeniedHandler instance.
    element access-denied-handler {access-denied-handler.attlist, empty}
access-denied-handler.attlist &= (ref | access-denied-handler-page)

access-denied-handler-page =
    ## The access denied page that an authenticated user will be redirected to if they request a page which they don't have the authority to access.
    attribute error-page {xsd:token}

intercept-url =
    ## Specifies the access attributes and/or filter list for a particular set of URLs.
    element intercept-url {intercept-url.attlist, empty}
intercept-url.attlist &=
    ## 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.
    attribute pattern {xsd:token}
intercept-url.attlist &=
    ## The access configuration attributes that apply for the configured path.
    attribute access {xsd:token}?
intercept-url.attlist &=
    ## The HTTP Method for which the access configuration attributes should apply. If not specified, the attributes will apply to any method.
    attribute method {"GET" | "DELETE" | "HEAD" | "OPTIONS" | "POST" | "PUT" | "TRACE"}?

intercept-url.attlist &=
    ## 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 filters created by the namespace configuration, and any added using 'custom-filter'), will be applied to any other paths.
    attribute filters {"none"}?
intercept-url.attlist &=
    ## Used to specify that a URL must be accessed over http or https, or that there is no preference. The value should be "http", "https" or "any", respectively.
    attribute requires-channel {xsd:token}?

logout =
    ## 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.
    element logout {logout.attlist, empty}
logout.attlist &=
    ## 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.
    attribute logout-url {xsd:token}?
logout.attlist &=
    ## Specifies the URL to display once the user has logged out. If not specified, defaults to /.
    attribute logout-success-url {xsd:token}?
logout.attlist &=
    ## Specifies whether a logout also causes HttpSession invalidation, which is generally desirable. If unspecified, defaults to true.
    attribute invalidate-session {xsd:boolean}?
logout.attlist &=
    ## A reference to a LogoutSuccessHandler implementation which will be used to determine the destination to which the user is taken after logging out.
    attribute success-handler-ref {xsd:token}?
logout.attlist &=
    ## A comma-separated list of the names of cookies which should be deleted when the user logs out
    attribute delete-cookies {xsd:token}?

request-cache =
    ## Allow the RequestCache used for saving requests during the login process to be set
    element request-cache {ref}

form-login =
    ## Sets up a form login configuration for authentication with a username and password
    element form-login {form-login.attlist, empty}
form-login.attlist &=
    ## The URL that the login form is posted to. If unspecified, it defaults to /j_spring_security_check.
    attribute login-processing-url {xsd:token}?
form-login.attlist &=
    ## The name of the request parameter which contains the username. Defaults to 'j_username'.
    attribute username-parameter {xsd:token}?
form-login.attlist &=
    ## The name of the request parameter which contains the password. Defaults to 'j_password'.
    attribute password-parameter {xsd:token}?
form-login.attlist &=
    ## 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.
    attribute default-target-url {xsd:token}?
form-login.attlist &=
    ## Whether the user should always be redirected to the default-target-url after login.
    attribute always-use-default-target {xsd:boolean}?
form-login.attlist &=
    ## 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.
    attribute login-page {xsd:token}?
form-login.attlist &=
    ## 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.
    attribute authentication-failure-url {xsd:token}?
form-login.attlist &=
    ## Reference to an AuthenticationSuccessHandler bean which should be used to handle a successful authentication request. Should not be used in combination with default-target-url (or always-use-default-target-url) as the implementation should always deal with navigation to the subsequent destination
    attribute authentication-success-handler-ref {xsd:token}?
form-login.attlist &=
    ## Reference to an AuthenticationFailureHandler bean which should be used to handle a failed authentication request. Should not be used in combination with authentication-failure-url as the implementation should always deal with navigation to the subsequent destination
    attribute authentication-failure-handler-ref {xsd:token}?
form-login.attlist &=
    ## Reference to an AuthenticationDetailsSource which will be used by the authentication filter
    attribute authentication-details-source-ref {xsd:token}?


openid-login =
    ## Sets up form login for authentication with an Open ID identity
    element openid-login {form-login.attlist, user-service-ref?, attribute-exchange*}

attribute-exchange =
    ## Sets up an attribute exchange configuration to request specified attributes from the OpenID identity provider. When multiple elements are used, each must have an identifier-attribute attribute. Each configuration will be matched in turn against the supplied login identifier until a match is found.
    element attribute-exchange {attribute-exchange.attlist, openid-attribute+}

attribute-exchange.attlist &=
    ## A regular expression which will be compared against the claimed identity, when deciding which attribute-exchange configuration to use during authentication.
    attribute identifier-match {xsd:token}?

openid-attribute =
    ## Attributes used when making an OpenID AX Fetch Request
    element openid-attribute {openid-attribute.attlist}

openid-attribute.attlist &=
    ## Specifies the name of the attribute that you wish to get back. For example, email.
    attribute name {xsd:token}
openid-attribute.attlist &=
    ## Specifies the attribute type. For example, http://axschema.org/contact/email. See your OP's documentation for valid attribute types.
    attribute type {xsd:token}
openid-attribute.attlist &=
    ## Specifies if this attribute is required to the OP, but does not error out if the OP does not return the attribute. Default is false.
    attribute required {xsd:boolean}?
openid-attribute.attlist &=
    ## Specifies the number of attributes that you wish to get back. For example, return 3 emails. The default value is 1.
    attribute count {xsd:int}?


filter-chain-map =
    ## Used to explicitly configure a FilterChainProxy instance with a FilterChainMap
    element filter-chain-map {filter-chain-map.attlist, filter-chain+}
filter-chain-map.attlist &=
    ## Deprecated. Use request-matcher instead.
    path-type?
filter-chain-map.attlist &=
    request-matcher?

filter-chain =
    ## Used within 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 assembled in a list in order to configure a FilterChainProxy, the most specific patterns must be placed at the top of the list, with  most general ones at the bottom.
    element filter-chain {filter-chain.attlist, empty}
filter-chain.attlist &=
    (pattern | request-matcher-ref)
filter-chain.attlist &=
    ## A comma separated list of bean names that implement Filter that should be processed for this FilterChain. If the value is none, then no Filters will be used for this FilterChain.
    attribute filters {xsd:token}

pattern =
    ## The request URL pattern which will be mapped to the FilterChain.
    attribute pattern {xsd:token}
request-matcher-ref =
    ## Allows a RequestMatcher instance to be used, as an alternative to pattern-matching.
    attribute request-matcher-ref {xsd:token}

filter-security-metadata-source =
    ## Used to explicitly configure a FilterSecurityMetadataSource 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.
    element filter-security-metadata-source {fsmds.attlist, intercept-url+}
fsmds.attlist &=
    use-expressions?
fsmds.attlist &=
    id?
fsmds.attlist &=
    ## Compare after forcing to lowercase
    attribute lowercase-comparisons {xsd:boolean}?
fsmds.attlist &=
    ## Deprecate. Use request-matcher instead.
    path-type?
fsmds.attlist &=
    request-matcher?

filter-invocation-definition-source =
    ## Deprecated synonym for filter-security-metadata-source
    element filter-invocation-definition-source {fsmds.attlist, intercept-url+}

http-basic =
    ## Adds support for basic authentication
    element http-basic {http-basic.attlist, empty}

http-basic.attlist &=
    ## Sets the AuthenticationEntryPoint which is used by the BasicAuthenticationFilter.
    attribute entry-point-ref {xsd:token}?
http-basic.attlist &=
    ## Reference to an AuthenticationDetailsSource which will be used by the authentication filter
    attribute authentication-details-source-ref {xsd:token}?

session-management =
    ## Session-management related functionality is implemented by the addition of a SessionManagementFilter to the filter stack.
    element session-management {session-management.attlist, concurrency-control?}

session-management.attlist &=
    ## 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".
    attribute session-fixation-protection {"none" | "newSession" | "migrateSession" }?
session-management.attlist &=
    ## The URL to which a user will be redirected if they submit an invalid session indentifier. Typically used to detect session timeouts.
    attribute invalid-session-url {xsd:token}?
session-management.attlist &=
    ## Allows injection of the SessionAuthenticationStrategy instance used by the SessionManagementFilter
    attribute session-authentication-strategy-ref {xsd:token}?
session-management.attlist &=
    ## Defines the URL of the error page which should be shown when the SessionAuthenticationStrategy raises an exception. If not set, an unauthorized (401) error code will be returned to the client. Note that this attribute doesn't apply if the error occurs during a form-based login, where the URL for authentication failure will take precedence.
    attribute session-authentication-error-url {xsd:token}?


concurrency-control =
    ## Enables concurrent session control, limiting the number of authenticated sessions a user may have at the same time.
    element concurrency-control {concurrency-control.attlist, empty}

concurrency-control.attlist &=
    ## The maximum number of sessions a single authenticated user can have open at the same time. Defaults to "1".
    attribute max-sessions {xsd:positiveInteger}?
concurrency-control.attlist &=
    ## The URL a user will be redirected to if they attempt to use a session which has been "expired" because they have logged in again.
    attribute expired-url {xsd:token}?
concurrency-control.attlist &=
    ## Specifies that an unauthorized error should be reported when a user attempts to login when they already have the maximum configured sessions open. The default behaviour is to expire the original session. If the session-authentication-error-url attribute is set on the session-management URL, the user will be redirected to this URL.
    attribute error-if-maximum-exceeded {xsd:boolean}?
concurrency-control.attlist &=
    ## Allows you to define an alias for the SessionRegistry bean in order to access it in your own configuration.
    attribute session-registry-alias {xsd:token}?
concurrency-control.attlist &=
    ## Allows you to define an external SessionRegistry bean to be used by the concurrency control setup.
    attribute session-registry-ref {xsd:token}?


remember-me =
    ## Sets up remember-me authentication. If used with the "key" attribute (or no attributes) the cookie-only implementation will be used. Specifying "token-repository-ref" or "remember-me-data-source-ref" will use the more secure, persisten token approach.
    element remember-me {remember-me.attlist}
remember-me.attlist &=
    ## The "key" used to identify cookies from a specific token-based remember-me application. You should set this to a unique value for your application.
    attribute key {xsd:token}?

remember-me.attlist &=
    (token-repository-ref | remember-me-data-source-ref | remember-me-services-ref)

remember-me.attlist &=
    user-service-ref?

remember-me.attlist &=
    ## Exports the internally defined RememberMeServices as a bean alias, allowing it to be used by other beans in the application context.
    attribute services-alias {xsd:token}?

remember-me.attlist &=
    ## Determines whether the "secure" flag will be set on the remember-me cookie. If set to true, the cookie will only be submitted over HTTPS (recommended). By default, secure cookies will be used if the request is made on a secure connection.
    attribute use-secure-cookie {xsd:boolean}?

remember-me.attlist &=
    ## The period (in seconds) for which the remember-me cookie should be valid.
    attribute token-validity-seconds {xsd:integer}?

remember-me.attlist &=
    ## Reference to an AuthenticationSuccessHandler bean which should be used to handle a successful remember-me authentication.
    attribute authentication-success-handler-ref {xsd:token}?


token-repository-ref =
    ## Reference to a PersistentTokenRepository bean for use with the persistent token remember-me implementation.
    attribute token-repository-ref {xsd:token}
remember-me-services-ref =
    ## Allows a custom implementation of RememberMeServices to be used. Note that this implementation should return RememberMeAuthenticationToken instances with the same "key" value as specified in the remember-me element. Alternatively it should register its own AuthenticationProvider. It should also implement the LogoutHandler interface, which will be invoked when a user logs out. Typically the remember-me cookie would be removed on logout.
    attribute services-ref {xsd:token}?
remember-me-data-source-ref =
    ## DataSource bean for the database that contains the token repository schema.
    data-source-ref

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 shared between the provider and filter. This generally does not need to be set. If unset, it will default to "doesNotMatter".
    attribute key {xsd:token}?
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".
    attribute username {xsd:token}?
anonymous.attlist &=
    ## 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".
    attribute granted-authority {xsd:token}?
anonymous.attlist &=
    ## With the default namespace setup, the anonymous "authentication" facility is automatically enabled. You can disable it using this property.
    attribute enabled {xsd:boolean}?


port-mappings =
    ## Defines the list of mappings between http and https ports for use in redirects
    element port-mappings {port-mappings.attlist, port-mapping+}

port-mappings.attlist &= empty

port-mapping =
    ## Provides a method to map http ports to https ports when forcing a redirect.
    element port-mapping {http-port, https-port}

http-port =
    ## The http port to use.
    attribute http {xsd:token}

https-port =
    ## The https port to use.
    attribute https {xsd:token}


x509 =
    ## Adds support for X.509 client authentication.
    element x509 {x509.attlist}
x509.attlist &=
    ## The regular expression used to obtain the username from the certificate's subject. Defaults to matching on the common name using the pattern "CN=(.*?),".
    attribute subject-principal-regex {xsd:token}?
x509.attlist &=
    ## Explicitly specifies which user-service should be used to load user data for X.509 authenticated clients. If ommitted, the default user-service will be used.
    user-service-ref?
x509.attlist &=
    ## Reference to an AuthenticationDetailsSource which will be used by the authentication filter
    attribute authentication-details-source-ref {xsd:token}?

jee =
    ## Adds a J2eePreAuthenticatedProcessingFilter to the filter chain to provide integration with container authentication.
    element jee {jee.attlist}
jee.attlist &=
    ## A comma-separate list of roles to look for in the incoming HttpServletRequest.
    attribute mappable-roles {xsd:token}
jee.attlist &=
    ## Explicitly specifies which user-service should be used to load user data for container authenticated clients. If ommitted, the set of mappable-roles will be used to construct the authorities for the user.
    user-service-ref?

authentication-manager =
    ## Registers the AuthenticationManager instance and allows its list of AuthenticationProviders to be defined. Also allows you to define an alias to allow you to reference the AuthenticationManager in your own beans.
    element authentication-manager {authman.attlist & authentication-provider* & ldap-authentication-provider*}
authman.attlist &=
    id?
authman.attlist &=
    ## An alias you wish to use for the AuthenticationManager bean (not required it you are using a specific id)
    attribute alias {xsd:token}?
authman.attlist &=
    ## If set to true, the AuthenticationManger will attempt to clear any credentials data in the returned Authentication object, once the user has been authenticated.
    attribute erase-credentials {xsd:boolean}?

authentication-provider =
    ## Indicates that the contained user-service should be used as an authentication source.
    element authentication-provider {ap.attlist & any-user-service & password-encoder?}
ap.attlist &=
    ## Specifies a reference to a separately configured AuthenticationProvider instance which should be registered within the AuthenticationManager.
    ref?
ap.attlist &=
    ## Specifies a reference to a separately configured UserDetailsService from which to obtain authentication data.
    user-service-ref?

user-service =
    ## Creates an in-memory UserDetailsService from a properties file or a list of "user" child elements. Usernames are converted to lower-case internally to allow for case-insensitive lookups, so this should not be used if case-sensitivity is required.
    element user-service {id? & (properties-file | (user*))}
properties-file =
    ## The location of a Properties file where each line is in the format of username=password,grantedAuthority[,grantedAuthority][,enabled|disabled]
    attribute properties {xsd:token}?

user =
    ## Represents a user in the application.
    element user {user.attlist, empty}
user.attlist &=
    ## The username assigned to the user.
    attribute name {xsd:token}
user.attlist &=
    ## 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). This attribute be omitted in the case where the data will not be used for authentication, but only for accessing authorities. If omitted, the namespace will generate a random value, preventing its accidental use for authentication. Cannot be empty.
    attribute password {xsd:string}?
user.attlist &=
    ## One of more authorities granted to the user. Separate authorities with a comma (but no space). For example, "ROLE_USER,ROLE_ADMINISTRATOR"
    attribute authorities {xsd:token}
user.attlist &=
    ## Can be set to "true" to mark an account as locked and unusable.
    attribute locked {xsd:boolean}?
user.attlist &=
     ## Can be set to "true" to mark an account as disabled and unusable.
    attribute disabled {xsd:boolean}?

jdbc-user-service =
    ## Causes creation of a JDBC-based UserDetailsService.
    element jdbc-user-service {id? & jdbc-user-service.attlist}
jdbc-user-service.attlist &=
    ## The bean ID of the DataSource which provides the required tables.
    attribute data-source-ref {xsd:token}
jdbc-user-service.attlist &=
    cache-ref?
jdbc-user-service.attlist &=
    ## An SQL statement to query a username, password, and enabled status given a username. Default is "select username,password,enabled from users where username = ?"
    attribute users-by-username-query {xsd:token}?
jdbc-user-service.attlist &=
    ## An SQL statement to query for a user's granted authorities given a username. The default is "select username, authority from authorities where username = ?"
    attribute authorities-by-username-query {xsd:token}?
jdbc-user-service.attlist &=
    ## An SQL statement to query user's group authorities given a username. The default is "select g.id, g.group_name, ga.authority from groups g, group_members gm, group_authorities ga where gm.username = ? and g.id = ga.group_id and g.id = gm.group_id"
    attribute group-authorities-by-username-query {xsd:token}?
jdbc-user-service.attlist &=
    role-prefix?


any-user-service = user-service | jdbc-user-service | ldap-user-service

custom-filter =
    ## Used to indicate that a filter bean declaration should be incorporated into the security filter chain.
    element custom-filter {custom-filter.attlist}

custom-filter.attlist &=
    ref

custom-filter.attlist &=
    (after | before | position)

after =
    ## 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.
    attribute after {named-security-filter}
before =
    ## The filter immediately before which the custom-filter should be placed in the chain
    attribute before {named-security-filter}
position =
    ## The explicit position at which the custom-filter should be placed in the chain. Use if you are replacing a standard filter.
    attribute position {named-security-filter}

named-security-filter = "FIRST" | "CHANNEL_FILTER" | "SECURITY_CONTEXT_FILTER" | "CONCURRENT_SESSION_FILTER" | "LOGOUT_FILTER" | "X509_FILTER" | "PRE_AUTH_FILTER" | "CAS_FILTER" | "FORM_LOGIN_FILTER" | "OPENID_FILTER" | "LOGIN_PAGE_FILTER" | "DIGEST_AUTH_FILTER" |"BASIC_AUTH_FILTER" | "REQUEST_CACHE_FILTER" | "SERVLET_API_SUPPORT_FILTER" | "JAAS_API_SUPPORT_FILTER" | "REMEMBER_ME_FILTER" | "ANONYMOUS_FILTER" | "SESSION_MANAGEMENT_FILTER" | "EXCEPTION_TRANSLATION_FILTER" | "FILTER_SECURITY_INTERCEPTOR" | "SWITCH_USER_FILTER" | "LAST"