$ the-wire · showcase
Spring Boot reactive resource server backs off with custom security
By RepoJournal · Filed · About Spring
Spring Boot's reactive OAuth2 resource server auto-configuration now backs off when a custom SecurityWebFilterChain is defined, matching servlet behavior.
Spring Boot's reactive OAuth2 resource server auto-configuration previously did not back off when a custom SecurityWebFilterChain was present, unlike the servlet equivalent [1]. This commit aligns the reactive auto-configuration with the servlet behavior, introducing the @ConditionalOnDefault annotation to handle the back-off.
Spring Kafka fixed an assignability ordering issue in its delegate map [2]. The TreeMap iteration order was undefined due to a non-transitive comparator; the lookup could return a more general delegate even when an exact one was registered. The fix ensures the most specific delegate is selected.
Spring Boot also fixed a bug in AppendableByteArray where a high surrogate left unconsumed by the encoder was dropped between append calls, causing surrogate pairs written a character at a time by JsonValueWriter to be corrupted [3]. Spring Session prepared for its 4.2 development version [4].
Action items
- → Review reactive resource server auto-config if you rely on custom SecurityWebFilterChain spring-projects/spring-boot [plan]
- → Upgrade Spring Kafka to include the delegate selection fix spring-projects/spring-kafka [plan]
- → Note that Spring Session is moving to 4.2 development spring-projects/spring-session [monitor]
References
- [1] Make reactive resource server back off with custom security ↗ spring-projects/spring-boot
- [2] GH-4624: Fix most-specific delegate selection ↗ spring-projects/spring-kafka
- [3] Fix corruption of supplementary characters in AppendableByteArray ↗ spring-projects/spring-boot
- [4] Prepare for 4.2 Development Version ↗ spring-projects/spring-session