Spring Security
- @PreFilter/@PreAuthorize/@PostFilter self-invocation method calls
Using @PreFilter/@PostFilter/@PreAuthorize: In proxy mode (which is the default), only external method calls coming in through the proxy are intercepted.
- Debug mode is activated in the Spring Security configuration
Reports activated <debug> that may expose sensitive information.
- Incorrect configuration of Spring beans referenced in the Spring Security annotation
Reports unresolved Spring beans referenced in Spring Security annotations.
- Incorrect Spring Security XML-based application context
Reports issues with the Spring Security XML-based context:.
- Obsolete request mapping format for Spring 7
Reports request patterns in Spring Security matcher methods that are incompatible with the PathPatternParser used by default since Spring Security 7.0.
- Request matcher configured after 'anyRequest()'
Reports request-matcher registrations (requestMatchers, mvcMatchers, antMatchers, regexMatchers) that are chained after anyRequest() inside an authorizeHttpRequests / authorizeRequests block.
- Unreachable Spring Security request matcher
Reports request matchers in an authorizeHttpRequests / authorizeRequests chain that are unreachable because an earlier, more general matcher already covers them.