Remove setAuthenticationManager from HttpSecurityConfiguration

[marcusdacoregio]

The @Autowired from that method was removed in #9256.
Since the method is not being used for anything else, it can be removed.

[jsh76]

Hi, there seems to be same autowire "bug" in Reactive class ServerHttpSecurityConfiguration.

[marcusdacoregio]

Hi @jsh76, the method in ServerHttpSecurityConfiguration is annotated with @Autowired(required = false), therefore we cannot remove it since it is being used.

[jsh76]

ok, I facing to this autowire "bug", when I add ReactiveAuthenticationManagerResolver with multiple definitions of ReactiveAuthenticationManager beans on my application.

I set one of my AuthManager beans with Primary -annotation to get application to startup. Does not know is there another way to get this running :)

[marcusdacoregio]

The method expects just one ReactiveAuthenticationManager, instead of a list you can create a ReactiveAuthenticationManager bean that is a combination of multiple ReactiveAuthenticationManagers, like DelegatingReactiveAuthenticationManager or RequestMatcherDelegatingAuthorizationManager.

[jsh76]

ok, thanks for help .. need to make some refactoring then :D