-
Notifications
You must be signed in to change notification settings - Fork 6k
WebClientReactiveClientCredentialsTokenResponseClient setWebClient #6051
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'd be interested in contributing. |
Sounds great, @jer051! The task is yours. |
I'd like to take the next ;) |
Same :) |
+1 |
Thanks to all those who are excited to contribute! I don't know of a good way of managing who gets dibs on first timer issues other than first come first serve. I think this is the fairest way to go about it. If you are on twitter I have been tweeting when a new first timer issue comes up. Alternatively, you can watch GitHub for the label to be added https://github.com/spring-projects/spring-security/labels/first-timers-only |
Added the ability to specify a custom WebClient in WebClientReactiveClientCredentialsTokenResponseClient. Also added testing to ensure the custom WebClient is not null and is used. Fixes: spring-projectsgh-6051
Added the ability to specify a custom WebClient in WebClientReactiveClientCredentialsTokenResponseClient. Also added testing to ensure the custom WebClient is not null and is used. Fixes: spring-projectsgh-6051
Added the ability to specify a custom WebClient in WebClientReactiveClientCredentialsTokenResponseClient. Also added testing to ensure the custom WebClient is not null and is used. Fixes: spring-projectsgh-6051
Added the ability to specify a custom WebClient in WebClientReactiveClientCredentialsTokenResponseClient. Also added testing to ensure the custom WebClient is not null and is used. Fixes: gh-6051
Summary
public void setWebClient(WebClient webClient)
method to WebClientReactiveClientCredentialsTokenResponseClient.null
cannot be passed inWebClient
is used if setThe text was updated successfully, but these errors were encountered: