From bb05603b3c2960d4ffa516ad30777ff25e8df379 Mon Sep 17 00:00:00 2001 From: Rob Winch Date: Tue, 12 May 2020 13:07:24 -0500 Subject: [PATCH] AbstractUserDetailsReactiveAuthenticationManager uses boundidElastic() Some JVMs have blocking operations when accessing SecureRandom and thus this needs to be performed in a pool that is larger than the number of CPUs Closes gh-7522 --- .../AbstractUserDetailsReactiveAuthenticationManager.java | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/core/src/main/java/org/springframework/security/authentication/AbstractUserDetailsReactiveAuthenticationManager.java b/core/src/main/java/org/springframework/security/authentication/AbstractUserDetailsReactiveAuthenticationManager.java index d32f7e6e20..cbc6e3b71b 100644 --- a/core/src/main/java/org/springframework/security/authentication/AbstractUserDetailsReactiveAuthenticationManager.java +++ b/core/src/main/java/org/springframework/security/authentication/AbstractUserDetailsReactiveAuthenticationManager.java @@ -55,7 +55,7 @@ public abstract class AbstractUserDetailsReactiveAuthenticationManager implement private ReactiveUserDetailsPasswordService userDetailsPasswordService; - private Scheduler scheduler = Schedulers.newParallel("password-encoder", Schedulers.DEFAULT_POOL_SIZE, true); + private Scheduler scheduler = Schedulers.boundedElastic(); private UserDetailsChecker preAuthenticationChecks = user -> { if (!user.isAccountNonLocked()) {