diff --git a/web/src/main/java/org/springframework/security/web/authentication/AbstractAuthenticationProcessingFilter.java b/web/src/main/java/org/springframework/security/web/authentication/AbstractAuthenticationProcessingFilter.java index 2ec631dcc7..8539aefa86 100644 --- a/web/src/main/java/org/springframework/security/web/authentication/AbstractAuthenticationProcessingFilter.java +++ b/web/src/main/java/org/springframework/security/web/authentication/AbstractAuthenticationProcessingFilter.java @@ -86,17 +86,16 @@ import org.springframework.web.filter.GenericFilterBean; * If authentication is successful, an {@link InteractiveAuthenticationSuccessEvent} will be published via the * application context. No events will be published if authentication was unsuccessful, because this would generally be * recorded via an {@code AuthenticationManager}-specific application event. - *
- * The filter has an optional attribute invalidateSessionOnSuccessfulAuthentication that will invalidate - * the current session on successful authentication. This is to protect against session fixation attacks (see - * this Wikipedia article for more information). - * The behaviour is turned off by default. Additionally there is a property migrateInvalidatedSessionAttributes - * which tells if on session invalidation we are to migrate all session attributes from the old session to a newly - * created one. This is turned on by default, but not used unless invalidateSessionOnSuccessfulAuthentication - * is true. If you are using this feature in combination with concurrent session control, you should set the - * sessionRegistry property to make sure that the session information is updated consistently. + * + *