解决Spring Security自定义filter重复执行问题

今天作项目的时候,发现每次拦截器日志都会打两遍,很纳闷,怀疑是Filter被执行了两遍。结果debug以后发现还真是!记录一下这个神奇的BUG!java

问题描述

项目中使用的是Spring-security做为权限框架,而后作了一个JwtAuthenticationTokenFilter做为拦截器拦截请求,校验Token,可是每次请求都会打两遍日志。下面是精简的源代码:spring

自定义的Filter类segmentfault

@Slf4j
@Component
public class JwtAuthenticationTokenFilter extends OncePerRequestFilter {

    @Override
    protected void doFilterInternal(
            HttpServletRequest request,
            HttpServletResponse response,
            FilterChain chain) throws ServletException, IOException {
        //...省略
        //打出两遍日志的地方
        log.info("User:{} request path:{}, method:{}, param:{}", username, request.getServletPath(),
                request.getMethod(), request.getParameterMap() == null ? null : OBJECT_MAPPER.writeValueAsString(request.getParameterMap()));
        //...省略
        chain.doFilter(request, response);
    }
}

WebSecurityConfig配置类mvc

@Configuration
@EnableWebSecurity
@EnableGlobalMethodSecurity(prePostEnabled = true)
public class WebSecurityConfig extends WebSecurityConfigurerAdapter {
    //...省略
    @Bean
    public JwtAuthenticationTokenFilter authenticationTokenFilterBean() throws Exception {
        return new JwtAuthenticationTokenFilter();
    }
    
        @Override
    protected void configure(HttpSecurity httpSecurity) throws Exception {
        //...省略
        //把JwtAuthenticationTokenFilter加入到RememberMeAuthenticationFilter以前
        httpSecurity.addFilterBefore(authenticationTokenFilterBean(), RememberMeAuthenticationFilter.class);
    }
    //...省略
}

请求日志以下:框架

问题解决

把自定义FilterJwtAuthenticationTokenFilter@Component取消掉就能够了,不让它被Spring容器管理。ide

缘由

在spring容器托管的OncePerRequestFilter的bean,都会自动加入到servlet的filter chain,而上面的定义,还额外把filter加入到了spring security的
ememberMeAuthenticationFilter以前。而spring security也是一系列的filter,在mvc的filter以前执行。所以在鉴权经过的状况下,就会前后各执行一次。debug

参考资料

解决spring security自定义filter重复执行问题日志

相关文章
相关标签/搜索