diff --git a/docs/manual/src/docbook/appendix-namespace.xml b/docs/manual/src/docbook/appendix-namespace.xml
index 2e34f199ff..b7b76b6dda 100644
--- a/docs/manual/src/docbook/appendix-namespace.xml
+++ b/docs/manual/src/docbook/appendix-namespace.xml
@@ -171,8 +171,8 @@
The <form-login> Element
- Used to add an UsernamePasswordAuthenticationProcessingFilter to
- the filter stack and an LoginUrlAuthenticationEntryPoint to the
+ Used to add an UsernamePasswordAuthenticationFilter to the
+ filter stack and an LoginUrlAuthenticationEntryPoint to the
application context to provide authentication on demand. This will always take precedence
over other namespace-created entry points. If no attributes are supplied, a login page will
be generated automatically at the URL "/spring-security-login" This feature
@@ -192,32 +192,32 @@
login-processing-url
Maps to the filterProcessesUrl property of
- UsernamePasswordAuthenticationProcessingFilter. The default value
- is "/j_spring_security_check".
+ UsernamePasswordAuthenticationFilter. The default value is
+ "/j_spring_security_check".
default-target-url
Maps to the defaultTargetUrl property of
- UsernamePasswordAuthenticationProcessingFilter. If not set, the
- default value is "/" (the application root). A user will be taken to this URL after
- logging in, provided they were not asked to login while attempting to access a secured
- resource, when they will be taken to the originally requested URL.
+ UsernamePasswordAuthenticationFilter. If not set, the default
+ value is "/" (the application root). A user will be taken to this URL after logging in,
+ provided they were not asked to login while attempting to access a secured resource, when
+ they will be taken to the originally requested URL.
always-use-default-target
If set to "true", the user will always start at the value given by
default-target-url, regardless of how they arrived at the login page.
Maps to the alwaysUseDefaultTargetUrl property of
- UsernamePasswordAuthenticationProcessingFilter. Default value is
- "false".
+ UsernamePasswordAuthenticationFilter. Default value is "false".
+
authentication-failure-url
Maps to the authenticationFailureUrl property of
- UsernamePasswordAuthenticationProcessingFilter. Defines the URL
- the browser will be redirected to on login failure. Defaults to
- "/spring_security_login?login_error", which will be automatically handled by the automatic
- login page generator, re-rendering the login page with an error message.
+ UsernamePasswordAuthenticationFilter. Defines the URL the browser
+ will be redirected to on login failure. Defaults to "/spring_security_login?login_error",
+ which will be automatically handled by the automatic login page generator, re-rendering
+ the login page with an error message.
authentication-success-handler-ref
@@ -384,8 +384,7 @@
The <openid-login> Element
Similar to <form-login> and has the same attributes. The
default value for login-processing-url is
- "/j_spring_openid_security_check". An
- OpenIDUsernamePasswordAuthenticationProcessingFilter and
+ "/j_spring_openid_security_check". An OpenIDAuthenticationFilter and
OpenIDAuthenticationProvider will be registered. The latter
requires a reference to a UserDetailsService. Again, this can
be specified by Id, using the user-service-ref attribute, or will be
diff --git a/docs/manual/src/docbook/cas-auth-provider.xml b/docs/manual/src/docbook/cas-auth-provider.xml
index 6c43334998..30d7e8e3ef 100644
--- a/docs/manual/src/docbook/cas-auth-provider.xml
+++ b/docs/manual/src/docbook/cas-auth-provider.xml
@@ -319,7 +319,7 @@
The CasProcessingFilter has very similar
- properties to the UsernamePasswordAuthenticationProcessingFilter
+ properties to the UsernamePasswordAuthenticationFilter
(used for form-based logins). Each property is
self-explanatory. Note that we've also used the namespace syntax
for setting up an alias to the authentication mnager, since the
diff --git a/docs/manual/src/docbook/concurrent-sessions.xml b/docs/manual/src/docbook/concurrent-sessions.xml
index 8c391121e4..668c73bdd5 100644
--- a/docs/manual/src/docbook/concurrent-sessions.xml
+++ b/docs/manual/src/docbook/concurrent-sessions.xml
@@ -44,7 +44,7 @@
+ class="org.springframework.security.web.authentcation.UsernamePasswordAuthenticationFilter">
...
@@ -106,7 +106,7 @@
+ class="org.springframework.security.web.authentcation.UsernamePasswordAuthenticationFilter">
...
diff --git a/docs/manual/src/docbook/core-filters.xml b/docs/manual/src/docbook/core-filters.xml
index 75d93f7095..e10705fe20 100644
--- a/docs/manual/src/docbook/core-filters.xml
+++ b/docs/manual/src/docbook/core-filters.xml
@@ -231,7 +231,7 @@ class="org.springframework.security.web.context.SecurityContextPersistenceFilter
- UsernamePasswordAuthenticationProcessingFilter
+ UsernamePasswordAuthenticationFilter
We've now seen the three main filters which are always present in a Spring Security
web configuration. These are also the three which are automatically created by the
namespace <http> element and cannot be substituted with
@@ -250,7 +250,7 @@ class="org.springframework.security.web.context.SecurityContextPersistenceFilter
ExceptionTranslationFilter.
Implement the login page (using a JSP or
MVC controller).Configure an instance of
- UsernamePasswordAuthenticationProcessingFilter in
+ UsernamePasswordAuthenticationFilter in
the application contextAdd the filter bean
to your filter chain proxy (making sure you pay attention to the order).
The login form simply
@@ -259,7 +259,7 @@ class="org.springframework.security.web.context.SecurityContextPersistenceFilter
/j_spring_security_check). The basic filter configuration looks
something like this:
+"org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter">
]]>
diff --git a/docs/manual/src/docbook/form-authentication.xml b/docs/manual/src/docbook/form-authentication.xml
index ed71e31d1e..fbd5aa133d 100644
--- a/docs/manual/src/docbook/form-authentication.xml
+++ b/docs/manual/src/docbook/form-authentication.xml
@@ -5,7 +5,7 @@
Overview
HTTP Form Authentication involves using the
- UsernamePasswordAuthenticationProcessingFilter to process a login
+ UsernamePasswordAuthenticationFilter to process a login
form. This is the most common way for an application to authenticate end
users. Form-based authentication is entirely compatible with the DAO, LDAP
and JAAS authentication providers.
@@ -21,10 +21,10 @@
j_password input fields, and posts to a URL that is
monitored by the filter (by default
/j_spring_security_check). You should add an
- UsernamePasswordAuthenticationProcessingFilter to your application context:
+ UsernamePasswordAuthenticationFilter to your application context:
+"org.springframework.security.web.authentication.UsernamePasswordAuthenticationFilter">
]]>
diff --git a/docs/manual/src/docbook/namespace-config.xml b/docs/manual/src/docbook/namespace-config.xml
index e20b303e99..dd2f2c003b 100644
--- a/docs/manual/src/docbook/namespace-config.xml
+++ b/docs/manual/src/docbook/namespace-config.xml
@@ -431,7 +431,7 @@
at particular locations or use a Spring Security filter for which there isn't currently a
namespace configuration option (CAS, for example). Or you might want to use a customized
version of a standard namespace filter, such as the
- UsernamePasswordAuthenticationProcessingFilter which is created by the
+ UsernamePasswordAuthenticationFilter which is created by the
<form-login> element, taking advantage of some of the extra
configuration options which are available by using the bean explicitly. How can you do this
with namespace configuration, since the filter chain is not directly exposed?
@@ -464,7 +464,7 @@
SubclassesN/A CAS_PROCESSING_FILTER
CasProcessingFilterN/A
AUTHENTICATION_PROCESSING_FILTER
- UsernamePasswordAuthenticationProcessingFilterhttp/form-login
+ UsernamePasswordAuthenticationFilterhttp/form-login
BASIC_PROCESSING_FILTER
BasicProcessingFilterhttp/http-basic
SERVLET_API_SUPPORT_FILTERSecurityContextHolderAwareRequestFilterhttp/@servlet-api-provision
diff --git a/docs/manual/src/docbook/remember-me-authentication.xml b/docs/manual/src/docbook/remember-me-authentication.xml
index 807def96a7..0815cb0af6 100644
--- a/docs/manual/src/docbook/remember-me-authentication.xml
+++ b/docs/manual/src/docbook/remember-me-authentication.xml
@@ -92,7 +92,7 @@
Remember-me authentication is not used with basic
authentication, given it is often not used with
HttpSessions. Remember-me is used with
- UsernamePasswordAuthenticationProcessingFilter, and is implemented
+ UsernamePasswordAuthenticationFilter, and is implemented
via hooks in the AbstractAuthenticationProcessingFilter
superclass. The hooks will invoke a concrete
RememberMeServices at the appropriate times. The
@@ -158,13 +158,13 @@
]]>
Don't forget to add your
RememberMeServices implementation to your
- UsernamePasswordAuthenticationProcessingFilter.setRememberMeServices()
+ UsernamePasswordAuthenticationFilter.setRememberMeServices()
property, include the
RememberMeAuthenticationProvider in your
AuthenticationManager.setProviders() list, and add
RememberMeProcessingFilter into your
FilterChainProxy (typically immediately after your
- UsernamePasswordAuthenticationProcessingFilter).
+ UsernamePasswordAuthenticationFilter).
PersistentTokenBasedRememberMeServices
diff --git a/docs/manual/src/docbook/security-filter-chain.xml b/docs/manual/src/docbook/security-filter-chain.xml
index 0fcb7cad47..4001170b77 100644
--- a/docs/manual/src/docbook/security-filter-chain.xml
+++ b/docs/manual/src/docbook/security-filter-chain.xml
@@ -151,7 +151,7 @@
Authentication processing mechanisms -
- UsernamePasswordAuthenticationProcessingFilter,
+ UsernamePasswordAuthenticationFilter,
CasProcessingFilter,
BasicProcessingFilter etc - so that the
SecurityContextHolder can be modified to contain a valid
diff --git a/docs/manual/src/docbook/web-infrastructure.xml b/docs/manual/src/docbook/web-infrastructure.xml
index d81e67be90..a49b59115b 100644
--- a/docs/manual/src/docbook/web-infrastructure.xml
+++ b/docs/manual/src/docbook/web-infrastructure.xml
@@ -154,7 +154,7 @@
Authentication processing mechanisms -
- UsernamePasswordAuthenticationProcessingFilter,
+ UsernamePasswordAuthenticationFilter,
CasProcessingFilter,
BasicProcessingFilter etc - so that the
SecurityContextHolder can be modified to contain a valid