Hmm,
I modified security.xml as suggested but I'm still getting the 302 response.
Here's the whole request/response:
--request--
POST /services/UserService HTTP/1.1
Content-Type: text/xml;charset=UTF-8
SOAPAction: ""
User-Agent: Jakarta Commons-HttpClient/3.0.1
Host: rad223:8080
Content-Length:
Thanks for your response.
I think you're right about the redirect because the 302 error refers to
login.jsp.
I'm using AppFuse 2.0.
I'm trying to test the webservice using SOAPUI-1.7.6 with WSS security
enabled - won't this work as a Client? I thought the Acegi security AppFuse
used was WSS compl
You're probably getting a redirect to the login page.
Assuming you can tell your web service clients to use Basic
Authentication (easy with PHP) your solution can be as simple as adding
a basicProcessingFilter to your acegi filter chain.
For AppFuse 1.9.x
in security.xml
filterChainProxy bean
This is now urgent! I've been trying for days to get secure web-services
going. I added /services/**=ROLE_ADMIN,ROLE_USER
to security.xml as advised and using WSS with SoapUI-1.7.6 I am only getting
an HTTP 302 response.
Please help!
George.Francis wrote:
>
> Once I've secured my Webservice b
Once I've secured my Webservice by editing WEB-INF/security.xml, how do I
test it?
I've been using SoapUI up until now but since the services are now secure
this fails (using WSS).
--
View this message in context:
http://www.nabble.com/secured-web-services-tf4673549s2369.html#a13352215
Sent fr
