Improve the problem of BeanPostProcessorChecker and not being able to boot SecurityAutoConfiguration when disabled. #257
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the current implementation, the following log is output at startup.
This is caused by the fact that
GrpcSecurityis initialized inGrpcSecurityConfiguration#setFileChainProxySecurityConfigurerand various beans are requested before BeanPostProcessor is created inGrpcSecurityConfiguration#bypassMethodInterceptorForGrpcMethodInvocation.Also, the problem of not booting when
org.springframework.boot.autoconfigure.security.servlet.SecurityAutoConfigurationis disabled will be improved.