Closed zyro23 closed 1 week ago
@zyro23
I add @EnableWebSocket
to file *Application.java
and app starts
hmm.. just added @EnableWebSocket
to DemoApplication
from the sample app but still getting the same error?
(gradle-) cleaned the project, re-ran multiple times.
to make sure this is not a "runs-on-my-machine" kinda issue:
enable-web-socket
to the sample repo, enabled github actions and added @EnableWebSocket
@zyro23
My bad, I work with wrong version, I confirm this version throws error
Can this issue be investigated before the releases of spring-security 6.4.0 and spring-boot 3.4.0 scheduled for next week? This problem breaks applications using both web and web sockets stacks.
@kalgon, I'm sorry that this didn't get it before the 6.4 release. The fix will go out in the 6.4.1 release. I'll consult with the team to see if we can get it moved up.
In the meantime, are you able to set spring.main.allow-bean-definition-overriding
to true
?
If not, while not ideal, you can remove @EnableWebSocketSecurity
, copy MessageMatcherAuthorizationManagerConfiguration
and WebSocketMessageBrokerSecurityConfiguration
into your project, and import them directly.
I've added https://github.com/spring-projects/spring-security-samples/issues/338 to catch things like this in the future.
Closed in favor of #16113
Describe the bug
the naming conflict is between:
To Reproduce
spring-security-messaging
as dependency@EnableWebSocketSecurity
Expected behavior
app starts
Sample
sample app will be referenced asap, thank you!