Spring Security Third Edition Secure Your Web Applications Restful Services And Microservice Architectures Review

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.

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. Most developers think they know Spring Security

Consider this common pattern:

If you take one concept from this book, make it this: “Authentication identifies who can knock. Authorization decides what they can touch. But in microservices, every internal call needs its own authorization – don’t trust the incoming token just because it’s signed.” Look at the book’s section on @CurrentSecurityContext to replace SecurityContextHolder boilerplate, and the chapter on reactive security for WebFlux – where even @PreAuthorize works differently than you expect. Sure, you removed HttpSession and added JWT tokens

True statelessness means the token carries all necessary information. Spring Security 3rd Edition introduces opaque tokens (via OpaqueTokenIntrospector ) as a better default for microservices, paired with signed JWTs only when you absolutely need client-parseable claims. “If you need to revoke a token before it expires, you don’t need JWTs – you need a session or an opaque token.” – Paraphrased from Chapter 8. 2. Method Security is Your Last Line of Defense – And You’re Ignoring It We all secure endpoints with @PreAuthorize("hasRole('ADMIN')") on controllers. But the book demonstrates a terrifying scenario: what if a vulnerability in a service layer method bypasses the controller entirely? Consider this common pattern: If you take one

Move @PreAuthorize to the service layer and use method security expressions that check both role and ownership: