- Shipped
- August 8, 2026 at 5:34 PM UTC
- Author
- Kamo
- Commit
- 33808d1
The service has not deployed since 2026-07-03; every pod since has crash-looped before the context loaded: This method cannot decide whether these patterns are Spring MVC patterns or not ... there is more than one mappable servlet in your servlet context: {DispatcherServlet=[/], **************** kamo-shared-library 1.5.0 now pulls spring-ws-core 4.0.6 transitively, so Spring Boot auto-registers a second servlet. With two mappable servlets Spring Security 6 will not guess whether a bare requestMatchers("/x/**") is MVC or Ant, and throws while building the filter chain. SecurityConfig itself never changed -- the classpath under it did. Declaring the patterns as AntPathRequestMatcher removes the ambiguity and is immune to whatever the shared library pulls in next. Behaviour is unchanged: the chain still permits everything, and authorization stays hand-rolled per handler. AuthorizationService, EmailService and KamoLOS use the same bare-string pattern and will hit this on their next deploy.