Can you post the full tomcat stack trace ? Expected behavior is to send a
SOAP Fault in this scenario. Seems something goes wrong in the fault flow.
thanks,
nandana
2009/2/14 TomazM tomaz.majerh...@arnes.si
I want it to return an XML that shows the SOAP Fault returned, so the
client
I use rampart 1.4 sample policy/sample02 and deployed in Tomcat and run client.
Stack:
2009-02-14 11:02:24,819 [http-8080-1] INFO
org.apache.xml.security.signature.Reference - Verification successful for URI
#Id-33320514
2009-02-14 11:02:24,819 [http-8080-1] INFO
I try rampart 1.4 sample/policy/sample02 with my wrong keystore and client
receive xml fault response:
soapenv:Fault
xmlns:wsse=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd;
faultcodewsse:InvalidSecurity/faultcode
faultstringThe certificate used for the
I want it to return an XML that shows the SOAP Fault returned, so the client
understand, how can I achieve this?
I have situation:
java 1.6_10
Tomcat 6.0.18
axis2_1_4
rampart 1.4
Client send soap message with wrong signed key and rampart return the response
is html, more precisely I get
