如何不在不安全的控制器之前调用 OncePerRequestFilter

发布于 2025-01-13 16:17:04 字数 1856 浏览 4 评论 0原文

我正在关注 示例< /a> 有 代码<我根据 href="https://stackoverflow.com/questions/36795894/how-to-apply-spring-security-filter-only-on-secured-endpoints">spring-security-filter-only-on-secured-endpoints

    @Override
    protected void configure(HttpSecurity http) throws Exception {
        http.antMatcher("/secureSide/**")
           .cors().and()
           .sessionManagement()
             .sessionCreationPolicy(SessionCreationPolicy.IF_REQUIRED)
             .and().addFilterBefore(tokenAuthenticationFilter(), UsernamePasswordAuthenticationFilter.class)
              .csrf().disable()
              .formLogin().disable()
              .httpBasic().disable()
              .exceptionHandling().authenticationEntryPoint(restAuthenticationEntryPoint())
              .and().authorizeRequests()
              .anyRequest().authenticated();
    }

和两个独立的控制器 但是

@RestController
@RequestMapping("/secureSide")
@EnableAutoConfiguration(exclude = SecurityAutoConfiguration.class)
public class SecureController {
...
}



@RestController
@RequestMapping("/completelyOpen")
public class OpenController {
...
}

当客户端调用 OpenController 中定义的端点时, doFilterInternal 仍然被调用,即使应该为 SecureController 调用过滤器

那么如何调用 doFilterInternal ( ofTokenFilter extends OncePerRequestFilter )被阻止?

I am following an example that has code that I modified per spring-security-filter-only-on-secured-endpoints
.

    @Override
    protected void configure(HttpSecurity http) throws Exception {
        http.antMatcher("/secureSide/**")
           .cors().and()
           .sessionManagement()
             .sessionCreationPolicy(SessionCreationPolicy.IF_REQUIRED)
             .and().addFilterBefore(tokenAuthenticationFilter(), UsernamePasswordAuthenticationFilter.class)
              .csrf().disable()
              .formLogin().disable()
              .httpBasic().disable()
              .exceptionHandling().authenticationEntryPoint(restAuthenticationEntryPoint())
              .and().authorizeRequests()
              .anyRequest().authenticated();
    }

and two Separate controllers
as

@RestController
@RequestMapping("/secureSide")
@EnableAutoConfiguration(exclude = SecurityAutoConfiguration.class)
public class SecureController {
...
}



@RestController
@RequestMapping("/completelyOpen")
public class OpenController {
...
}

But when end points defined in OpenController are called by the client, the doFilterInternal still gets called, even though the filter are supposed to be called for SecureController

So how can the call to doFilterInternal ( ofTokenFilter extends OncePerRequestFilter ) be prevented?

如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。

扫码二维码加入Web技术交流群

发布评论

需要 登录 才能够评论, 你可以免费 注册 一个本站的账号。
列表为空,暂无数据
我们使用 Cookies 和其他技术来定制您的体验包括您的登录状态等。通过阅读我们的 隐私政策 了解更多相关信息。 单击 接受 或继续使用网站,即表示您同意使用 Cookies 和您的相关数据。
原文