2012-08-12 76 views
3

根据文章Spring Security: Redirect to invalid-session-url instead of logout-success-url on successful logout,注销会话时,Spring Security重定向到用户定义的无效会话URL。春季安全注销重定向到注销成功,然后立即成为无效会话页面

<session-management invalid-session-url="/invalidSession.jsp"> 
    <concurrency-control max-sessions="1" error-if-maximum-exceeded="true" /> 
</session-management> 

然而,如果注销,成功URL设置

<logout invalidate-session="true" 
      logout-success-url="/logoutSuccess.jsp" 
      logout-url="/logout" /> 

春天仍然重定向到无效的会话URL重定向到注销,成功URL后。即使logoutSuccess url不安全,也会发生这种情况。即,

<intercept-url pattern="/logoutSuccess.jsp*" access="permitAll"/> 

这是Spring bug吗?由于logout-success-url已设置且不安全,因此在达到注销成功url后,用户似乎不应该被重定向到无效会话url。

日志如下所示:

INFO: [DEBUG,SimpleUrlLogoutSuccessHandler] Using default Url: /logoutSuccess.jsp 
INFO: [DEBUG,DefaultRedirectStrategy] Redirecting to '/Application/logoutSuccess.jsp' 
INFO: [DEBUG,HttpSessionSecurityContextRepository] SecurityContext is empty or contents are anonymous - context will not be stored in HttpSession. 
INFO: [DEBUG,SecurityContextPersistenceFilter] SecurityContextHolder now cleared, as request processing completed 
INFO: [DEBUG,FilterChainProxy] /logoutSuccess.jsp at position 1 of 10 in additional filter chain; firing Filter: 'ConcurrentSessionFilter' 
INFO: [DEBUG,FilterChainProxy] /logoutSuccess.jsp at position 2 of 10 in additional filter chain; firing Filter: 'SecurityContextPersistenceFilter' 
INFO: [DEBUG,HttpSessionSecurityContextRepository] No HttpSession currently exists 
INFO: [DEBUG,HttpSessionSecurityContextRepository] No SecurityContext was available from the HttpSession: null. A new one will be created. 
INFO: [DEBUG,FilterChainProxy] /logoutSuccess.jsp at position 3 of 10 in additional filter chain; firing Filter: 'LogoutFilter' 
INFO: [DEBUG,FilterChainProxy] /logoutSuccess.jsp at position 4 of 10 in additional filter chain; firing Filter: 'UsernamePasswordAuthenticationFilter' 
INFO: [DEBUG,FilterChainProxy] /logoutSuccess.jsp at position 5 of 10 in additional filter chain; firing Filter: 'RequestCacheAwareFilter' 
INFO: [DEBUG,FilterChainProxy] /logoutSuccess.jsp at position 6 of 10 in additional filter chain; firing Filter: 'SecurityContextHolderAwareRequestFilter' 
INFO: [DEBUG,FilterChainProxy] /logoutSuccess.jsp at position 7 of 10 in additional filter chain; firing Filter: 'AnonymousAuthenticationFilter' 
INFO: [DEBUG,AnonymousAuthenticationFilter] Populated SecurityContextHolder with anonymous token: 'org.sprin[email protected]9055c2bc: Principal: anonymousUser; Credentials: [PROTECTED]; Authenticated: true; Details: org.sprin[email protected]b364: RemoteIpAddress: 0:0:0:0:0:0:0:1; SessionId: null; Granted Authorities: ROLE_ANONYMOUS' 
INFO: [DEBUG,FilterChainProxy] /logoutSuccess.jsp at position 8 of 10 in additional filter chain; firing Filter: 'SessionManagementFilter' 
INFO: [DEBUG,SessionManagementFilter] Requested session ID a396530a530b344ff531ab657e32 is invalid. 
INFO: [DEBUG,SimpleRedirectInvalidSessionStrategy] Starting new session (if required) and redirecting to '/invalidsession.jsp' 
INFO: [DEBUG,HttpSessionEventPublisher] Publishing event: org.springframework.security.web.session.HttpSessionCreatedEvent[[email protected]0] 
INFO: [DEBUG,DefaultRedirectStrategy] Redirecting to '/Application/invalidsession.jsp' 

回答

6

这在reference manual解释。总之,“无效会话”功能基于提交的会话cookie的有效性,所以如果您在注销后访问站点(或更具体地说是安全筛选器链),并且您仍有JSESSIONID cookie,您可能会触发此不良行为。

如手动的相同部分所描述的,你可以尝试使用

<logout invalidate-session="true" 
     logout-success-url="/logoutSuccess.jsp" 
     logout-url="/logout" delete-cookies="JSESSIONID" /> 

注销时删除的cookie。

+0

谢谢,阅读手册中的部分后有意义。 – Colin 2012-08-12 13:10:56

2

你要小心了,有时用invalidate-session='true'delete-cookies=JSESSIONID连同用户可以拥有会话数限制以来,可能让你当您尝试登录,即使“1最大会话这主要超标”错误在您注销后。

建议您只使用Delete-cookies删除必要的会话信息,当您使用Spring Security 3.1及更高版本时。