Spring Security Allow instantiation with a custom webclient

Expected Behavior

Allow the passing in of a custom WebClient when instantiating any child of the class AbstractWebClientReactiveOAuth2AccessTokenResponseClient.

Current Behavior

Currently have the overhead of having to first instantiate it with a default WebClient and then the setting of the required custom one. It is also the only place where a WebClient is explicitly instantiated.

Closed PR from before I raised issue (my bad) - https://github.com/spring-projects/spring-security/pull/13772

Comment From: jzheaux

Thanks for the suggestion, @TuranDev. What aspects of the overhead are giving your application problems? Since Spring Security tends to only include non-defaulted parameters in the constructor, I want to make sure that we are addressing the correct issue.

Comment From: spring-projects-issues

If you would like us to look at this issue, please provide the requested information. If the information is not provided within the next 7 days this issue will be closed.

Comment From: spring-projects-issues

Closing due to lack of requested feedback. If you would like us to look at this issue, please provide the requested information and we will re-open the issue.