Let’s explore three counterintuitive lessons from the book that will change how you think about securing modern applications. The book opens with a provocative claim: Most developers misuse stateless authentication.
Most developers think they know Spring Security. You add the dependency, configure a UserDetailsService , maybe tweak some CORS settings, and call it done. But the third edition of Spring Security by Laurentiu Spilca reveals a harsh truth: that basic setup leaves your REST APIs and microservices dangerously exposed. Let’s explore three counterintuitive lessons from the book
Consider this common pattern:
// Simplified from Chapter 11 JwtAuthenticationToken token = ...; Set<String> allowedScopes = getScopesForCurrentService(); Jwt trimmedJwt = JwtHelper.trimScopes(token.getToken(), allowedScopes); This way, payment-service never sees scopes like profile:write – reducing lateral movement risk if compromised. The third edition isn’t about adding more filters. It’s about understanding where authorization actually happens – at the method level, between services, and even inside SQL queries (using Spring Data’s @PostFilter sparingly, as the book warns). You add the dependency, configure a UserDetailsService ,
Sure, you removed HttpSession and added JWT tokens. But did you accidentally reintroduce state via your database? Every time you query a token_blacklist table or hit Redis to validate a session-like JWT, you’ve created state – and with it, scalability bottlenecks. The third edition isn’t about adding more filters