Generate Server Side Implementation based on WSDL
Hi mail group, I have just started at a new job. My work includes maintaning our business server (java based J2EE container) Previously all our business components have been written first (straigth up POJO) and then they have been rigistred to the Axis2 run-time envionrment using the AxisConfiguration API. (e.g. we have never handled any configuration xml files / WSDL etc) But this week I got the WSDL file for a business service that we are required to support. This means that we must either be able to generate the java classes directly based on the WSDL definitons, or to somehow configure the mapping between the standard WSDL data definitions into Java. I'm pretty new to this so any help is greatly appreciated. But I cannot change the fact all the registration is done using the AxisConfiguration API, to change this would require to much work. BR Niels _ Kolla mailen när du är på språng - skaffa Hotmail i mobilen! http://windowslivemobile.msn.com/BrowserServiceHotmail.aspx?lang=SE-SE
Re: axis rampart fault response as XML
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 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
Re: MTOM file upload webservice
Can you post the service code (Method signature)? thanks, nandana On Fri, Feb 13, 2009 at 2:10 AM, Attharkar, Asmita aatth...@telcordia.comwrote: Hi, I am trying to write a web service which uploads a file so that it can be retrieved by the client. Most of the articles that I have read talks about file upload web service using SwA. My Web service is uploading the file with no issues and adding it to outMsgContext (like the eg shown for SwA) but I am having problem receiving it on the client side. My web service doesn't contain any argument which stands for the attachment/data Handler). Any help is appreciated. Thanks, Asmita -- (Tel) 732-699-4657 | 4B566 | Telcordia Technologies | Piscataway NJ 08854 -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
Re: Generate Server Side Implementation based on WSDL
Hi Niels, This tutorial [1] will help you. thanks, nandana [1] - http://wso2.org/node/2873 On Sun, Feb 15, 2009 at 4:30 PM, Niels Boem me.softw...@hotmail.com wrote: Hi mail group, I have just started at a new job. My work includes maintaning our business server (java based J2EE container) Previously all our business components have been written first (straigth up POJO) and then they have been rigistred to the Axis2 run-time envionrment using the AxisConfiguration API. (e.g. we have never handled any configuration xml files / WSDL etc) But this week I got the WSDL file for a business service that we are required to support. This means that we must either be able to generate the java classes directly based on the WSDL definitons, or to somehow configure the mapping between the standard WSDL data definitions into Java. I'm pretty new to this so any help is greatly appreciated. But I cannot change the fact all the registration is done using the AxisConfiguration API, to change this would require to much work. BR Niels -- Krama någon i vinter! Hitta kärleken här! MSN Dejtinghttp://match.se.msn.com/channel/index.aspx?trackingid=1002952 -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
Re: Rampart - axis2 fault
Hi Kumar, You have set the actions to UsernameToken Timestamp but your SOAP UI is a missing a timestamp in the security header. That is the reason for the actions mismatch error. Can you configure the SOAP UI to send a timestamp as well and try again. Hopefully that will solve the problem. thanks, nandana On Tue, Feb 10, 2009 at 2:59 AM, Iyengar, Kumar kumar_iyen...@bmc.comwrote: Thanks Nandana for the quick response. Here is the XML that Soap UI sends. I have set the action in services.xml to 'UsernameToken Timestamp' and so SoapUI is sending the password bobPW as a digest Host: localhost:8080 Content-Length: 1053 SOAPAction: urn:echo User-Agent: Jakarta Commons-HttpClient/3.0.1 Content-Type: text/xml;charset=UTF-8 soapenv:Envelope xmlns:sam=http://sample02.samples.rampart.apache.org; xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; soapenv:Header wsse:Security soapenv:mustUnderstand=1 xmlns:wsse= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd wsse:UsernameToken wsu:Id=UsernameToken-2960804 xmlns:wsu= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd wsse:Usernamebob/wsse:Username wsse:Password Type= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest b+iddlgeF2hcpof8WQ/iEYo5QEw=/wsse:Password wsse:NonceB1NdVICiOB2XBBZHQ66ijg==/wsse:Nonce wsu:Created2009-02-09T21:16:43.652Z/wsu:Created /wsse:UsernameToken /wsse:Security /soapenv:Header soapenv:Body sam:echo !--Optional:-- sam:param0How R U/sam:param0 /sam:echo /soapenv:Body /soapenv:Envelope I will look at the samples. Unfortunately at this point, I have to get an app working (with Username Token and eventually X509) without depending on Policy. I installed the Sample02, 03 onto a Tomcat server that has Axis2 installed along with Rampart. I can get a simple request without any username token working with SoapUI as the client. Thanks for any help, --kumar -- *From:* Nandana Mihindukulasooriya [mailto:nandana@gmail.com] *Sent:* Monday, February 09, 2009 12:07 PM *To:* axis-user@ws.apache.org *Subject:* Re: Rampart - axis2 fault Hi Kumar, Can you please post the SOAP message sent by SOAP UI ? Anyway if you starting to use Rampart, I would recommend you to use policy based approach which is more interoperable and most of the development for new specifications is only available in the policy based configuration. You can look at Rampart policy samples in the binary distribution and these two articles in WSO2 Oxygen Tank will also help you to get started. http://wso2.org/library/3190 https://wso2.org/library/3415 thanks, nandana On Tue, Feb 10, 2009 at 1:12 AM, Iyengar, Kumar kumar_iyen...@bmc.com wrote: Hi all, Thanks for the help earlier. I managed to get a bit further. I am trying to get the Rampart sample programs working but am getting the following error: [ERROR] WSDoAllReceiver: security processing failed (actions mismatch) org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed (actions mismatch) at org.apache.rampart.handler.WSDoAllReceiver.processBasic(WSDoAllReceiver.java:344) at org.apache.rampart.handler.WSDoAllReceiver.processMessage(WSDoAllReceiver.java:86) at org.apache.rampart.handler.WSDoAllHandler.invoke(WSDoAllHandler.java:72) 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.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:709) at javax.servlet.http.HttpServlet.service(HttpServlet.java:802) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107) at
Re: Axis2(1.4) + Rampart 1.4 usage
Actually you can with WS-Security Policy 1.2. PasswordDigest can be configured only using WS Security Policy 1.2. Can you please try with WS Security Policy 1.2 configuration ? thanks, nandana On Thu, Feb 12, 2009 at 3:12 AM, Landslide xiangm...@landslide.com wrote: Can anyone help confirm that I can not do PasswordDigest with Axis2 using policy on the client side? Thanks! -- View this message in context: http://www.nabble.com/Axis2%281.4%29-%2B-Rampart-1.4-throws-exception-tp17877253p21964907.html Sent from the Axis - User mailing list archive at Nabble.com. -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
Re: Ramapart Config based dynamic client sample code
Please get the AxisOperation/AxisMessage and from that you can get the
PolicySubject. Attach the policy to the PolicySubject. I will check whether
there is a sample documented somewhere.
thanks,
nandana
On Wed, Feb 11, 2009 at 12:25 AM, Wishing Carebear
wishing.careb...@gmail.com wrote:
Can someone give some pointers please.
Thanks,
cbear
On Mon, Feb 9, 2009 at 3:42 PM, Wishing Carebear
wishing.careb...@gmail.com wrote:
Hello:Hoping someone could reply.
Thanks for your time,
Regards,
cbear
On Mon, Feb 9, 2009 at 11:42 AM, Wishing Carebear
wishing.careb...@gmail.com wrote:
Could someone give some pointers.
Thanks,
cbear
On Fri, Feb 6, 2009 at 4:27 PM, Wishing Carebear
wishing.careb...@gmail.com wrote:
Hello:The OutflowConfiguration that works right now looks like below:
private static Parameter getOutflowConfiguration() {
OutflowConfiguration ofc = new OutflowConfiguration();
ofc.setActionItems(Encrypt);
ofc.setEncryptionUser(service);
ofc.setEncryptionPropFile(client.properties);
return ofc.getProperty();
}
Since the OutflowConfiguration is deprecated, would like to use
RampartConfiguration is possible. Don't have any policy defined for the
service. Found some examples of RampartConfig() as below:
private static Policy getRampartConfig(){
RampartConfig rampartConfig = new RampartConfig();
rampartConfig.setUser(client);
rampartConfig.setPwCbClass(samples.quickstart.clients.PWCBHandler);
CryptoConfig sigCrypto = new CryptoConfig();
sigCrypto.setProvider(org.apache.ws.security.components.crypto.Merlin);
Properties props = new Properties();
props.setProperty(org.apache.ws.security.crypto.merlin.keystore.type,
JKS);
props.setProperty(org.apache.ws.security.crypto.merlin.file,client.jks);
props.setProperty(org.apache.ws.security.crypto.merlin.keystore.password,
clientPW);
sigCrypto.setProp(props);
rampartConfig.setSigCryptoConfig(sigCrypto);
Policy policy = new Policy();
policy.addAssertion(rampartConfig);
return policy;
}
But don't know how to bind this to the OperationClient. I also have to
encrypt the request and decrycpt the response messages.
Thanks,
cbear
On Fri, Feb 6, 2009 at 10:46 AM, Wishing Carebear
wishing.careb...@gmail.com wrote:
Hello:Noticed that the OutflowConfiguration and InFlowConfiguration
classes are deprectaed.
Trying to see if RampartConfig could be used to get the same behavior.
Saw the policy based examples but could not find any code that could add
the
Rampart code programmitically.
1) Please point me to some examples where the RampartConfig is done
programmitically
2) I use the OperationClient to invoke webservices. Would like to add
the RampartConfig() to that. Is it possible
3) Also would like to know the equivalent of OutFlow and InFlow
configuration handlers using the RampartConfig.
Thanks for your help and time,
Regards
cabear
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
Re: Axis2 Fault - actions mismatch
Cause for this error is that the security header in the request doesn't match the configured actions. Please verify by looking at the request and configured actions. thanks, nandana On Sun, Feb 8, 2009 at 4:29 AM, Iyengar, Kumar kumar_iyen...@bmc.comwrote: Hi all, I have setup Axis2 and am trying to use one of the standard examples for Username Token. I keep getting this error: org.apache.axis2.AxisFault: WSDoAllReceiver: security processing failed (actions mismatch). Does anyone know how to resolve this? I use SOAP UI 2.0.1 to send the request in. Any help is appreciated. Thanks, --kumar -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
Re: Applying policies at binding hierarchy in Apache Axis2 1.4.1/Rampart 1.4
Hi Alexis, Sorry I just saw the mail. I will have a look at your WSDL11ToAxisServiceBuilder and see why the policy is not being attached correctly. thanks, nandana On Thu, Feb 12, 2009 at 10:21 AM, Alexis Midon mi...@intalio.com wrote: (forwarding to the rampart folks) Alexis -- Forwarded message -- From: Alexis Midon mi...@intalio.com Date: Tue, Feb 10, 2009 at 5:50 PM Subject: Applying policies at binding hierarchy in Apache Axis2 1.4.1/Rampart 1.4 To: axis-user@ws.apache.org Hi everyone, based on this article: http://wso2.org/library/3786, I wrote my own (simple) wsdl with a policy attached to the soap binding. I load that wsdl with a WSDL11ToAxisServiceBuilder [1]. My issue is that when I invoke the service the following AxisFault is thrown: org.apache.axis2.AxisFault: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd: Security at org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:102) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:166) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) After a debugging session, it appears that the policy map of the AxisService holds a policy reference, but the policy include and subject do not. And the policy is never accessed by the RampartReceiver. Could you tell what I'm missing and/or point me to a working sample of embedded policy (I did not find any in Rampart repo)? Thanks in advance, Alexis [1] http://github.com/matthieu/apache-ode/blob/085025ab3639c7aa0255bbb9b905210ff6caf295/axis2/src/main/java/org/apache/ode/axis2/hooks/ODEAxisService.java#L80 -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
RE: Axis2 Fault - actions mismatch
nearest I can tell you have there exists mismatch parameter mismatch for Inflow
(actions) and Outflow (actions)
protected boolean checkReceiverResults(Vector wsResult, Vector actions) {
int resultActions = wsResult.size();
int size = actions.size();
-
+
// if (size != resultActions) {
// throw new AxisFault(
// WSDoAllReceiver: security processing failed (actions number
// mismatch));
// }
-
+
int ai = 0;
for (int i = 0; i resultActions; i++) {
int act = ((WSSecurityEngineResult) wsResult.get(i)).getAction();
@@ -256,14 +257,14 @@
}
HTH
Martin
__
Disclaimer and confidentiality note
Everything in this e-mail and any attachments relates to the official business
of Sender. This transmission is of a confidential nature and Sender does not
endorse distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
Date: Mon, 16 Feb 2009 05:17:25 +0530
Subject: Re: Axis2 Fault - actions mismatch
From: nandana@gmail.com
To: axis-user@ws.apache.org
Cause for this error is that the security header in the request doesn't match
the configured actions. Please verify by looking at the request and configured
actions.
thanks,
nandana
On Sun, Feb 8, 2009 at 4:29 AM, Iyengar, Kumar kumar_iyen...@bmc.com wrote:
Hi all,
I have setup Axis2 and am trying to use one of the standard
examples for Username Token. I keep getting this error:
org.apache.axis2.AxisFault: WSDoAllReceiver: security
processing failed (actions mismatch).
Does anyone know how to resolve this? I use SOAP UI 2.0.1 to
send the request in.
Any help is appreciated.
Thanks,
--kumar
--
Nandana Mihindukulasooriya
WSO2 inc.
http://nandana83.blogspot.com/
http://www.wso2.org
_
Windows Live™: E-mail. Chat. Share. Get more ways to connect.
http://windowslive.com/howitworks?ocid=TXT_TAGLM_WL_t2_allup_howitworks_022009
Re: Applying policies at binding hierarchy in Apache Axis2 1.4.1/Rampart 1.4
I can't wait for your feedback, and may be a working sample ;) Thanks a lot Nandana! Alexis On Sun, Feb 15, 2009 at 3:49 PM, Nandana Mihindukulasooriya nandana@gmail.com wrote: Hi Alexis, Sorry I just saw the mail. I will have a look at your WSDL11ToAxisServiceBuilder and see why the policy is not being attached correctly. thanks, nandana On Thu, Feb 12, 2009 at 10:21 AM, Alexis Midon mi...@intalio.com wrote: (forwarding to the rampart folks) Alexis -- Forwarded message -- From: Alexis Midon mi...@intalio.com Date: Tue, Feb 10, 2009 at 5:50 PM Subject: Applying policies at binding hierarchy in Apache Axis2 1.4.1/Rampart 1.4 To: axis-user@ws.apache.org Hi everyone, based on this article: http://wso2.org/library/3786, I wrote my own (simple) wsdl with a policy attached to the soap binding. I load that wsdl with a WSDL11ToAxisServiceBuilder [1]. My issue is that when I invoke the service the following AxisFault is thrown: org.apache.axis2.AxisFault: Must Understand check failed for header http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd: Security at org.apache.axis2.engine.AxisEngine.checkMustUnderstand(AxisEngine.java:102) at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:166) at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275) After a debugging session, it appears that the policy map of the AxisService holds a policy reference, but the policy include and subject do not. And the policy is never accessed by the RampartReceiver. Could you tell what I'm missing and/or point me to a working sample of embedded policy (I did not find any in Rampart repo)? Thanks in advance, Alexis [1] http://github.com/matthieu/apache-ode/blob/085025ab3639c7aa0255bbb9b905210ff6caf295/axis2/src/main/java/org/apache/ode/axis2/hooks/ODEAxisService.java#L80 -- Nandana Mihindukulasooriya WSO2 inc. http://nandana83.blogspot.com/ http://www.wso2.org
is axis2c supported on mainframes
Hi, we want to write webservices on mainframes using axis2c. I wonder if axis2c supports mainframes and if supports is there anything special need to take care of? -- Thanks Regards Pradeep Patel
Re: [axis2] Multiref client request to axis2 service
Any ideas on how multi ref soap envelope could be parsed on server side? Amila Suriarachchi wrote: On Tue, Feb 10, 2009 at 11:50 AM, Ashwini Chavan acha...@vertex.co.in mailto:acha...@vertex.co.in wrote: I am still stuck on this. Can someone help me? Does axis2 support multi-ref soap request? it does not support this. and soap encoding. thanks, Amila. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy the original message all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email. Please do not print this email unless it is absolutely necessary. -- Forwarded message -- From: Ashwini Chavan acha...@vertex.co.in mailto:acha...@vertex.co.in To: axis-...@ws.apache.org mailto:axis-...@ws.apache.org Date: Fri, 06 Feb 2009 11:17:39 +0530 Subject: [axis2] Multiref client request to axis2 service I am newbie to webservice. My axis2 webservice is generated using wsdl2java tool with XMLBeans data binding extension. Webservice client is sending multiref soap envelope in the request. My WSDL is document/encoded. I have attached my WSDL file and the client request soap envelope that I receive. I am receiving the values of input parameters as null in the service. Can someone help me to find out why? Do I need to do any more changes? please help Also, in the web service response, content-length is not getting set. My web service is deployed on tomcat. I also tested this with the standalone axis2 server. My client request is using HTTP/1.0 protocol and hence tranfer-encoding chunked is disabled. Any response should be of great help. Thanks and regards, ?xml version=1.0 encoding=UTF-8? soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/; xmlns:xsd=http://www.w3.org/2001/XMLSchema; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; soapenv:Body ns1:getIPAddress soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns1=http://www.example.org/test/; data href=#id0 / /ns1:provisionComplete multiRef id=id0 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns2:data xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; xmlns:ns2=http://www.example.org/test/; name xsi:type=xsd:string100.100.100.100/name statusCode href=#id1 / /multiRef multiRef id=id1 soapenc:root=0 soapenv:encodingStyle=http://schemas.xmlsoap.org/soap/encoding/; xsi:type=ns3:statusCode xmlns:ns3=http://www.example.org/test/; xmlns:soapenc=http://schemas.xmlsoap.org/soap/encoding/; 1 /multiRef /soapenv:Body /soapenv:Envelope -- Amila Suriarachchi WSO2 Inc. blog: http://amilachinthaka.blogspot.com/ -- *Ashwini Chavan : Cell 9890573363* Technical Leader Vertex Software Pvt. Ltd. (An NTT DATA Company) Creating Value E-mail: acha...@vertex.co.in Website: www.vertexsoft.com Server Space, 5th 6th Floor, AG Technology Park, Off ITI Road, Aundh, Pune - 411 007, Maharashtra, India Phone: +91-20-66041500 X 718 Fax: +91-20-66041621. The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy the original message all copies of this message and any attachments. WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any
Re: axis rampart fault response as XML
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 org.apache.xml.security.signature.Reference - Verification successful for URI #Timestamp-9838079 2009-02-14 11:02:24,866 [http-8080-1] ERROR org.apache.axis2.engine.AxisEngine - The certificate used for the signature is not trusted 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.AxisServlet.doPost(AxisServlet.java:133) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:286) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:845) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:583) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) 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) ... 19 more 2009-02-14 11:02:24,897 [http-8080-1] INFO org.apache.axis2.transport.http.AxisServlet - org.apache.axis2.AxisFault: Error in extracting message properties 2009-02-14 11:06:47,945 [http-8080-1] INFO org.apache.xml.security.signature.Reference - Verification successful for URI #Id-33320514 2009-02-14 11:06:47,945 [http-8080-1] INFO org.apache.xml.security.signature.Reference - Verification successful for URI #Timestamp-9838079 service.xml service name=SignedHeaderBody description Podpisemo header in body, ni pa kriptiran /description operation name=echo messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation operation name=sestej messageReceiver class=org.apache.axis2.rpc.receivers.RPCMessageReceiver/ /operation parameter name=ServiceClass locked=falserampart1_4.sample02.service.PojoService/parameter module ref=rampart / module ref=addressing / policy ... /service policy config: wsp:Policy wsu:Id=SigOnly xmlns:wsu=http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd; xmlns:wsp=http://schemas.xmlsoap.org/ws/2004/09/policy; wsp:ExactlyOne wsp:All sp:AsymmetricBinding xmlns:sp=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy; wsp:Policy sp:InitiatorToken wsp:Policy sp:X509Token sp:IncludeToken=http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient; wsp:Policy sp:RequireThumbprintReference/ sp:WssX509V3Token10/ /wsp:Policy /sp:X509Token
Re: axis rampart fault response as XML
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 signature is not trusted/faultstring detail Exceptionorg.apache.axis2.AxisFault: The certificate used for the signature is not trusted#13; at org.apache.rampart.handler.RampartReceiver.setFaultCodeAndThrowAxisFault(RampartReceiver.java:166)#13; at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:99)#13; at org.apache.axis2.engine.Phase.invoke(Phase.java:317)#13; at org.apache.axis2.engine.AxisEngine.invoke(AxisEngine.java:264)#13; at org.apache.axis2.engine.AxisEngine.receive(AxisEngine.java:163)#13; at org.apache.axis2.transport.http.HTTPTransportUtils.processHTTPPostRequest(HTTPTransportUtils.java:275)#13; at org.apache.axis2.transport.http.HTTPWorker.service(HTTPWorker.java:278)#13; at org.apache.axis2.transport.http.server.AxisHttpService.doService(AxisHttpService.java:281)#13; at org.apache.axis2.transport.http.server.AxisHttpService.handleRequest(AxisHttpService.java:187)#13; at org.apache.axis2.transport.http.server.HttpServiceProcessor.run(HttpServiceProcessor.java:82)#13; at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1061)#13; at edu.emory.mathcs.backport.java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:575)#13; at java.lang.Thread.run(Thread.java:619)#13; Caused by: org.apache.rampart.RampartException: The certificate used for the signature is not trusted#13; at org.apache.rampart.PolicyBasedResultsValidator.validate(PolicyBasedResultsValidator.java:174)#13; at org.apache.rampart.RampartEngine.process(RampartEngine.java:204)#13; at org.apache.rampart.handler.RampartReceiver.invoke(RampartReceiver.java:92)#13; ... 11 more#13; /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 tomaz.majerh...@arnes.si mailto:tomaz.majerh...@arnes.si 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:tomaz.majerh...@arnes.si 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
