Instrument (Reactive)AuthorizationManager

[jzheaux]

[Shabin]

When moving from spring 5 to 6 for one of our legacy applications, the change in HttpSecurityBeanDefinitionParser.java which added a ChildAuthenticationManagerFactoryBean factory bean messed up the bean creation order of the application. Since this is a factory bean, it got eagerly initialized during one of a bean postprocessor creation and hence our xml based http security userdetails service bean also got initialized before autowiring postprocessor was created and hence the autowired beans inside in our userdetails resulted in null.

I tried to avoid our custom bean postprocessor which was not required now. But then had another issue from a AbstractBeanFactoryPointcutAdvisor bean which had a StaticMethodMatcherPointcut autowired inside it. Is it not recommended to autowire pointcut inside an advisor? We have lots of similar advisor beans which have autowired pointcut beans.

It will be very difficult for us to change the bean ordering or advisors since it a complicated legacy application. Any option to fall back to the original ProviderManager based security initialization if observability is not required?

[nucleussoftwareopen]

@jzheaux , I am facing the same problem as mentioned by @Shabin.