Skip to content
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

SEC-2853: Rename WebSocket XML Namespace elements #3075

spring-projects-issues opened this issue Feb 17, 2015 · 1 comment

SEC-2853: Rename WebSocket XML Namespace elements #3075

spring-projects-issues opened this issue Feb 17, 2015 · 1 comment


Copy link

@spring-projects-issues spring-projects-issues commented Feb 17, 2015

Rob Winch (Migrated from SEC-2853) said:

We should rename <security:messages> to <security:websocket-message-broker> because while the underlying interceptors will work with messages the XML namespace relies on specifics of Spring's websocket namespace. Similarly we should rename <security:message-interceptor> to <security:interceptor-message> to align with Spring Security's <interceptor-method> and <interceptor-url>.

Copy link

@andremrezende andremrezende commented Dec 22, 2016

I am using spring version 4.1.0.RELEASE, my security.xml is:

<security:http pattern="/resources/**" security="none" />
<security:http pattern="images/**" security="none" />
<security:http pattern="/app/error/**" security="none" />

	<security:intercept-message type="CONNECT" access="permitAll"/>
	<security:intercept-message type="UNSUBSCRIBE" access="permitAll" />
	<security:intercept-message type="DISCONNECT" access="permitAll" />
	<security:intercept-message pattern="/**" access="permitAll" />
And the error continues: Offending resource: ServletContext resource [/WEB-INF/spring/root-context.xml]; nested exception is org.springframework.beans.factory.parsing.BeanDefinitionParsingException: Configuration problem: Security namespace does not support decoration of element [websocket-message-broker]

How Could i fix it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants