Bean Conflict Between webSocketAuthorizationManagerPostProcessor
and objectPostProcessor
in Spring Security Configuration
#16299
Labels
Describe the bug
The application fails to start due to a conflict between two beans required by the declare Bean
SecurityFilterChain
. The method expects a single bean, but two candidates are found:webSocketAuthorizationManagerPostProcessor
Defined in:
WebSocketObservationConfiguration.class
objectPostProcessor
Defined in:
ObjectPostProcessorConfiguration.class
This conflict causes Spring to throw an error during startup, indicating an inability to resolve the ambiguity.
This issue occurs in Spring Security 6.4.2.
To Reproduce
@EnableWebSocketSecurity
.APPLICATION FAILED TO START
Expected behavior
The application should start successfully without bean injection conflicts.
Sample
A link to a GitHub repository with a minimal, reproducible sample.
The text was updated successfully, but these errors were encountered: