如何解决Spring Security JWT认证中公共资源访问返回403的问题
问题场景
在Spring Boot API项目中基于Spring Security实现JWT身份认证时,访问公共接口返回403错误。
已完成的配置
- 自定义
WebSecurityConfigurerAdapter实现类,配置放行auth/**路径下的所有资源 - 已通过配置主动禁用
csrf()防护,排除CSRF拦截导致的403
异常现象
向/auth/login路径发起POST请求时,配置的公共访问规则未生效,直接返回403拒绝访问。
DEBUG模式核心日志
Request received for POST '/auth/login?username=wally&password=wally': org.apache.catalina.connector.RequestFacade@585d8cc6 servletPath:/auth/login pathInfo:null headers: user-agent: PostmanRuntime/7.26.8 accept: */* postman-token: 91c2a071-a353-4d77-9c7c-b04a43b94081 host: localhost:8091 accept-encoding: gzip, deflate, br connection: keep-alive content-length: 0 Security filter chain: [ WebAsyncManagerIntegrationFilter SecurityContextPersistenceFilter HeaderWriterFilter LogoutFilter JwtFilter RequestCacheAwareFilter SecurityContextHolderAwareRequestFilter AnonymousAuthenticationFilter SessionManagementFilter ExceptionTranslationFilter FilterSecurityInterceptor ] ************************************************************ 2020-12-22 20:21:15.919 DEBUG 6288 --- [nio-8091-exec-2] o.s.security.web.FilterChainProxy : Securing POST /auth/login?username=wally&password=wally 2020-12-22 20:21:15.937 DEBUG 6288 --- [nio-8091-exec-2] s.s.w.c.SecurityContextPersistenceFilter : Set SecurityContextHolder to empty SecurityContext 2020-12-22 20:21:15.948 DEBUG 6288 --- [nio-8091-exec-2] s.s.w.c.SecurityContextPersistenceFilter : Cleared SecurityContextHolder to complete request 2020-12-22 20:21:15.960 INFO 6288 --- [nio-8091-exec-2] Spring Security Debugger : ************************************************************ Request received for POST '/error?username=wally&password=wally': org.apache.catalina.core.ApplicationHttpRequest@6d88bc8c servletPath:/error pathInfo:null headers: user-agent: PostmanRuntime/7.26.8 accept: */* postman-token: 91c2a071-a353-4d77-9c7c-b04a43b94081 host: localhost:8091 accept-encoding: gzip, deflate, br connection: keep-alive content-length: 0 Security filter chain: [ WebAsyncManagerIntegrationFilter SecurityContextPersistenceFilter HeaderWriterFilter LogoutFilter JwtFilter RequestCacheAwareFilter SecurityContextHolderAwareRequestFilter AnonymousAuthenticationFilter SessionManagementFilter ExceptionTranslationFilter FilterSecurityInterceptor ] ************************************************************ 2020-12-22 20:21:15.961 DEBUG 6288 --- [nio-8091-exec-2] o.s.security.web.FilterChainProxy : Securing POST /error?username=wally&password=wally 2020-12-22 20:21:15.961 DEBUG 6288 --- [nio-8091-exec-2] s.s.w.c.SecurityContextPersistenceFilter : Set SecurityContextHolder to empty SecurityContext 2020-12-22 20:21:15.967 DEBUG 6288 --- [nio-8091-exec-2] o.s.s.w.a.AnonymousAuthenticationFilter : Set SecurityContextHolder to anonymous SecurityContext 2020-12-22 20:21:15.998 DEBUG 6288 --- [nio-8091-exec-2] o.s.s.w.a.i.FilterSecurityInterceptor : Failed to authorize filter invocation [POST /error?username=wally&password=wally] with attributes [authenticated] 2020-12-22 20:21:16.022 DEBUG 6288 --- [nio-8091-exec-2] o.s.s.w.a.Http403ForbiddenEntryPoint : Pre-authenticated entry point called. Rejecting access 2020-12-22 20:21:16.025 DEBUG 6288 --- [nio-8091-exec-2] s.s.w.c.SecurityContextPersistenceFilter : Cleared SecurityContextHolder to complete request
日志关键观察点
- 针对
/auth/login的原始请求,在安全过滤器链处理过程中,没有走完后续的匿名认证、授权校验环节就直接中断,服务端将请求转发到了/error路径 - 最终返回的403响应,是转发后的
/error路径触发的拦截:该路径的访问规则要求必须完成认证才能访问,匿名请求被拒绝 - 配置的
auth/**路径放行规则没有被触发,说明问题出在授权规则匹配之前的请求处理环节
内容的提问来源于stack exchange,提问作者Wall-E
相关产品推荐
相关产品推荐

