intermediary adding soap header element breaking signature verification
Here is the soap message after it is signed using AXIS 1.4, WSS4J 1.5: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"; elementEncoding="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"; wsu:Id="binarytoken"> 123MIIB5jCCAU8CBEQyyzkwDQYJKoZIhvcNAQEFBQAwOjELMAkGA1UEBhMCVVMxDTALBgNVBAoTBEFN http://www.w3.org/2000/09/xmldsig#";> http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/> http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/> http://www.w3.org/2000/09/xmldsig#sha1"/> EwE9/d/aFPCf7CpqoKdbHSrhNN0= lCIbgyn1nzA/7Y2tAVQ+WuVTX/WoOKE0Xv1dOTDBJ+BIY1w6ulg17apQ2taLmfDHGEFtLOCO TKdvhev5CMNCvmsbZQVv5Mli+ttFSpumNf8yOkf0BwDCcSyTVbuiotJJXOFVGRTXB5oxIv8q UqY5QO3lZkO790OmUyBlpgWaWAE= http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"/> http://transfer.as.com";> http://shr.ws.com"; xsi:nil="true"/> Say if I use AXIS + WSS4J on bother sender side and receiver side and say if an intermediary adds an element 0d88d3e0-0e2c-489d-a682-da14b8fec3d7 to the soap header and after adding this element the complete soap message looks like below: http://schemas.xmlsoap.org/soap/envelope/"; xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; xmlns:xsd="http://www.w3.org/2001/XMLSchema"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xmlns:intermediary="http://www.intermediary.com/proxy/2424.2424s";> 0d88d3e0-0e2c-489d-a682-da14b8fec3d7 http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd";> http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"; elementEncoding="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"; wsu:Id="binarytoken"> 123MIIB5jCCAU8CBEQyyzkwDQYJKoZIhvcNAQEFBQAwOjELMAkGA1UEBhMCVVMxDTALBgNVBAoTBEFN http://www.w3.org/2000/09/xmldsig#";> http://www.w3.org/TR/2001/REC-xml-c14n-20010315#WithComments"/> http://www.w3.org/2000/09/xmldsig#rsa-sha1"/> http://www.w3.org/TR/2001/REC-xml-c14n-20010315"/> http://www.w3.org/2000/09/xmldsig#sha1"/> EwE9/d/aFPCf7CpqoKdbHSrhNN0= lCIbgyn
Re: Axis2 v1.0: Namespace prefix error
Thanks for the feedback. I will check in on the wstx mailing list. Do you know the version of WSTX that Axis2 uses?
TIA.On 8/12/06, Ajith Ranabahu <[EMAIL PROTECTED]> wrote:
Hi,Hmm.. the error popped up from the underlying pull parser ! A WSTXimplementation issue perhaps ?AjithOn 8/11/06, D P <[EMAIL PROTECTED]
> wrote:> Hello everyone:>> Axis2 v1.0> CF 7.0>> I'm attempting to send the following SOAP message through cold fusion to a> service I've written.>> SOAP message:
>> > xmlns:soapenv="> http://schemas.xmlsoap.org/soap/envelope/">> xmlns:ns1="http://webservices.company.com/credential "> xmlns="http://webservices.company.com/credential
"> soapenv:mustUnderstand="0"> soapenv:actor="">872)(@nNjDU{> xmlns:ns2="> http://webservices.company.com/notification/">2006-08-09T11:09:29.809ZServer
> Name:> testStartnotifyOfError()Operation> Description:> testStartnotifyOfError()Here is a> message:> testStartnotifyOfError()
>> When axis2 attempts to parse the credential element into an object, I get> the following error:>> com.ctc.wstx.exc.WstxParsingException: Undeclared namespace> prefix "soapenv" (for attribute "actor")
>> The problem goes away when I add the soapenv namespace declaration on the> credential element. I don't understand why I need to, since I thought the> actor attribute would inherit its namespace from the soapenv namespace
> declared on the soap:Envelope element. Can someone please explain, as I feel> I'm missing something here?>> TIA.--Ajith Ranabahu-
To unsubscribe, e-mail: [EMAIL PROTECTED]For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Axis2] Bizarre chunked thing
Hi, Have you looked at the messages through TCPMon (just to make sure the payload is chunked or not) ? Ajith On 8/11/06, Brecht Yperman <[EMAIL PROTECTED]> wrote: Hi, when using Axis-1.0, I had to put (CHUNKED = true) to call the Google Webservice client.getOptions().setProperty(MessageContextConstants.CHUNKED, new Boolean(true)); otherwise I'd get a java.net.SocketException: Software caused connection abort: recv failed; Now I'm using the snapshot (aug 10) and MessageContextConstants.CHUNKED is deprecated, so I use HttpConstants.CHUNKED. client.getOptions().setProperty(HTTPConstants.CHUNKED, new Boolean(false)); The bizarre thing is, now I have to set it to false otherwise I get the same exception... It's not really a problem ofcourse, but I thought I'd mention it. Brecht Invenso - The "Integration Software" specialists. _ Brecht Yperman Development team Direct: +32 (0)3 780 30 05 Email: [EMAIL PROTECTED] INVENSO bvba Industriepark-West 75 9100 Sint-Niklaas Belgium - Europe Phone: +32 (0)3 780 30 02 Fax: +32 (0)3 780 30 03 Email: [EMAIL PROTECTED] Website: www.invenso.com "E-mail disclaimer: This e-mail, and any attachments thereto, is intended only for use by the addressee(s) named herein and may contain legally privileged and/or confidential information. If you are not the intended recipient, please note that any review, dissemination, disclosure, alteration, printing, copying or transmission of this e-mail and/or any file transmitted with it, is strictly prohibited and may be unlawful. If you have received this e-mail by mistake, please immediately notify the sender and permanently delete the original as well as any copy of any e-mail and any printout thereof." - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Ajith Ranabahu - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis2 v1.0: Namespace prefix error
Hi,
Hmm.. the error popped up from the underlying pull parser ! A WSTX
implementation issue perhaps ?
Ajith
On 8/11/06, D P <[EMAIL PROTECTED]> wrote:
Hello everyone:
Axis2 v1.0
CF 7.0
I'm attempting to send the following SOAP message through cold fusion to a
service I've written.
SOAP message:
http://schemas.xmlsoap.org/soap/envelope/";>http://webservices.company.com/credential "
xmlns="http://webservices.company.com/credential";
soapenv:mustUnderstand="0"
soapenv:actor="">872)(@nNjDU{http://webservices.company.com/notification/";>2006-08-09T11:09:29.809ZServer
Name:
testStartnotifyOfError()Operation
Description:
testStartnotifyOfError()Here is a
message:
testStartnotifyOfError()
When axis2 attempts to parse the credential element into an object, I get
the following error:
com.ctc.wstx.exc.WstxParsingException: Undeclared namespace
prefix "soapenv" (for attribute "actor")
The problem goes away when I add the soapenv namespace declaration on the
credential element. I don't understand why I need to, since I thought the
actor attribute would inherit its namespace from the soapenv namespace
declared on the soap:Envelope element. Can someone please explain, as I feel
I'm missing something here?
TIA.
--
Ajith Ranabahu
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Attachment Support in Axis 1.4
Hi,
i am playing around with the attchment support with Axis 1.4. The first
question is, what is the current status of MTOM support in Axis 1.4. I was able
to send attachment with MTOM-Encoding so far and I would like to know if there
is any limitation and whether MTOM is officially and fully supported. The 2
question is about message style with attachment. Using RPC/Encoded, I am able
to send call a service method containing a single parameter, which is a bean
containg a DataHandler-attribut, which stands for the attachment. But when
switching to Wrapped by calling call.setOperationStyle(Style.WRAPPED) on the
client side, I get the following exception, which actually occurs on the client
side. It seems the BeanSerializer, which I have regsitered before, can't be
found.
My question is: why can't the bean serializer registration can't be found any
more? Is it possible to use wrapped with attachment at all?
StackTrace:
- Exception:
AxisFault
faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
faultSubcode:
faultString: java.io.IOException: No serializer found for class
de.javamagazin.attachments.FileWrapper in registry [EMAIL PROTECTED]
faultActor:
faultNode:
faultDetail:
{http://xml.apache.org/axis/}stackTrace:java.io.IOException: No
serializer found for class de.javamagazin.attachments.FileWrapper in registry
[EMAIL PROTECTED]
at
org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1507)
at
org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
at
org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
at
org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
at
org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
at
org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
at org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
at
org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(AttachmentsImpl.java:554)
at org.apache.axis.Message.getContentType(Message.java:486)
at
org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:343)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
de.javamagazin.attachments.FileWrapperUploadServiceClient.main(FileWrapperUploadServiceClient.java:55)
{http://xml.apache.org/axis/}hostname:SAMSUNG
java.io.IOException: No serializer found for class
de.javamagazin.attachments.FileWrapper in registry [EMAIL PROTECTED]
at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:317)
at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
at org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
at
org.apache.axis.attachments.AttachmentsImpl.getAttachmentCount(AttachmentsImpl.java:554)
at org.apache.axis.Message.getContentType(Message.java:486)
at
org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:343)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
at
org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
at org.apache.axis.client.Call.invoke(Call.java:2767)
at org.apache.axis.client.Call.invoke(Call.java:2443)
at org.apache.axis.client.Call.invoke(Call.java:2366)
at org.apache.axis.client.Call.invoke(Call.java:1812)
at
de.javamagazin.attachments.FileWrapperUploadServiceClient.main(FileWrapperUploadServiceClient.java:55)
Caused by: java.io.IOException:
