You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the configuration of MessageDispatcherServlet
there is no way to restrict the endpoint access.
The problem is that I want to create security-constraint for the Actual Service calls, but have my WSDLs open.
I have this on web.xml:
<servlet>
<servlet-name>spring-ws</servlet-name>
<servlet-class>org.springframework.ws.transport.http.MessageDispatcherServlet</servlet-class>
...
</servlet>
<servlet-mapping>
<servlet-name>spring-ws</servlet-name>
<url-pattern>/services/*</url-pattern>
But when I use my client using endpoint http://myserver/myapp/services/test.wsdl, MessageDispatcher does not filter that it is a wsdl Call, and still executes my Endpoint Method.
I would expect only returning the wsdl in this URL call.
Affects: 2.2.1
The text was updated successfully, but these errors were encountered:
Daniel Conde Diehl opened SWS-899 and commented
In the configuration of MessageDispatcherServlet
there is no way to restrict the endpoint access.
The problem is that I want to create security-constraint for the Actual Service calls, but have my WSDLs open.
I have this on web.xml:
<servlet>
<servlet-name>spring-ws</servlet-name>
<servlet-class>org.springframework.ws.transport.http.MessageDispatcherServlet</servlet-class>
...
</servlet>
<servlet-mapping>
<servlet-name>spring-ws</servlet-name>
<url-pattern>/services/*</url-pattern>
But when I use my client using endpoint http://myserver/myapp/services/test.wsdl, MessageDispatcher does not filter that it is a wsdl Call, and still executes my Endpoint Method.
I would expect only returning the wsdl in this URL call.
Affects: 2.2.1
The text was updated successfully, but these errors were encountered: