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";> <faultcode>wsse:InvalidSecurity</faultcode> <faultstring>The certificate used for the signature is not trusted</faultstring> <detail> <Exception>org.apache.axis2.AxisFault: The certificate used for the signature is not trusted at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:166) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99) at org.apache.axis2.engine.Phase.invoke(Phase.java:317) at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:278) at org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281) at org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187) at org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061) at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575) at java.lang.Thread.run(Thread.java:619) Caused by: org.apache.rampart.RampartException: The certificate used for the signature is not trusted at org.apache.rampart.PolicyBasedResultsValidator.validate(PolicyBasedResultsValidator.java:174) at org.apache.rampart.RampartEngine.process(RampartEngine.java:204) at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92) ... 11 more </Exception> What is the key configuration for this behavior, so I must config axis2 in my Tomcat? Regards, Tomaz Nandana Mihindukulasooriya wrote: > 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 <[email protected] > <mailto:[email protected]>> > > 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 Tomcat response: > > HTTP Status 500 > The server encountered an internal error () that prevented it from > fulfilling this request. > > > In axis2 log: > > ERROR org.apache.axis2.engine.AxisEngine - The certificate used for > the signature is not trusted > > > Is there any configuration of service or rampart to return SOAP xml > message with fault response:'The certificate used for the signature > is not > trusted' or fault_code so the client could read this message? > > > Regards, Tomaz > > > > > > > -- > Nandana Mihindukulasooriya > WSO2 inc. > > http://nandana83.blogspot.com/ > http://www.wso2.org
begin:vcard fn:Tomaz Majerhold n:Majerhold;Tomaz org:ARNES, Slovenian NREN;Development team adr:;;Jamova 39;Ljubljana;Ljubljana;1000;Slovenia email;internet:[email protected] title:Developer tel;work:+386 14798930 tel;fax:+386 1 479 88 99 tel;home:+386 1425 38 01 tel;cell:+386 40757229 url:http://www.arnes.si/ version:2.1 end:vcard
