Skip to content

ReactiveMethodSecurityConfiguration not eligible for auto-proxying #27962

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

Closed
anmgarg opened this issue Sep 13, 2021 · 7 comments
Closed

ReactiveMethodSecurityConfiguration not eligible for auto-proxying #27962

anmgarg opened this issue Sep 13, 2021 · 7 comments

Comments

@anmgarg
Copy link

anmgarg commented Sep 13, 2021

Getting this while deployment

[main] INFO  org.springframework.context.support.PostProcessorRegistrationDelegate$BeanPostProcessorChecker.postProcessAfterInitialization():376 {} - Bean 'org.springframework.security.config.annotation.method.configuration.ReactiveMethodSecurityConfiguration' of type [org.springframework.security.config.annotation.method.configuration.ReactiveMethodSecurityConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

I faced this issue after upgrading to 2.5.1 Earlier, I was using 2.3.4.RELEASE version.

@spring-projects-issues spring-projects-issues added the status: waiting-for-triage An issue we've not yet triaged label Sep 13, 2021
@wilkinsona
Copy link
Member

Something has triggered eager initialization of ReactiveMethodSecurityConfiguration. This has resulted in it being initialized before all of the context's been post-processors which prevents if from being fully post-processed. This may or may not be a problem and we can't tell without some more information.

If you would like us to spend some more time investigating, please spend some time providing a complete yet minimal sample that reproduces the problem. You can share it with us by pushing it to a separate repository on GitHub or by zipping it up and attaching it to this issue.

@wilkinsona wilkinsona added the status: waiting-for-feedback We need additional information before we can continue label Sep 13, 2021
@spring-projects-issues
Copy link
Collaborator

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.

@spring-projects-issues spring-projects-issues added the status: feedback-reminder We've sent a reminder that we need additional information before we can continue label Sep 20, 2021
@spring-projects-issues
Copy link
Collaborator

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.

@spring-projects-issues spring-projects-issues removed status: waiting-for-feedback We need additional information before we can continue status: feedback-reminder We've sent a reminder that we need additional information before we can continue status: waiting-for-triage An issue we've not yet triaged labels Sep 27, 2021
@Marthym
Copy link

Marthym commented Jul 16, 2022

Hi,

I have the same problem when I add spring-boot-starter-actuator in classpath of a Webflux project.

I use @EnableReactiveMethodSecurity on my security config.

2022-07-16 17:22:10.803  INFO 22535 --- [           main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.security.config.annotation.method.configuration.ReactiveMethodSecurityConfiguration' of type [org.springframework.security.config.annotation.method.configuration.ReactiveMethodSecurityConfiguration] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

@philwebb
Copy link
Member

@Marthym can you please provide a sample application that shows the problem.

@Marthym
Copy link

Marthym commented Jul 18, 2022

demo-with-message.zip

Just add custum security config with spring-boot-starter-actuator

@philwebb Thanks for your help

@wilkinsona
Copy link
Member

Thanks for the sample, @Marthym. The log message appears to be due to a bug in Spring Security. I've opened spring-projects/spring-security#11596.

@wilkinsona wilkinsona removed their assignment Jul 19, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants