Hi Nandana, Following is the request sent by the Axis client:
------------------------------------------------------------------------------------ <?xml version='1.0' encoding='UTF-8'?> <soapenv:Envelope xmlns:soapenv="http://www.w3.org/2003/05/soap-envelope";> <soapenv:Header xmlns:wsa="http://www.w3.org/2005/08/addressing";> <wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"; soapenv:mustUnderstand="true"> <wsu:Timestamp xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="Timestamp-1800743798"> <wsu:Created>...</wsu:Created> <wsu:Expires>...</wsu:Expires> </wsu:Timestamp> <wsse:BinarySecurityToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"; ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"; wsu:Id="CertId-26742559">...</wsse:BinarySecurityToken> <ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"; Id="Signature-1507951819"> <ds:SignedInfo> <ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"; /> <ds:SignatureMethod Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1"; /> <ds:Reference URI="#Id-613975815"> <ds:Transforms> <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"; /> </ds:Transforms> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"; /> <ds:DigestValue>...</ds:DigestValue> </ds:Reference> <ds:Reference URI="#Timestamp-1800743798"> <ds:Transforms> <ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"; /> </ds:Transforms> <ds:DigestMethod Algorithm="http://www.w3.org/2000/09/xmldsig#sha1"; /> <ds:DigestValue>...</ds:DigestValue> </ds:Reference> </ds:SignedInfo> <ds:SignatureValue>...</ds:SignatureValue> <ds:KeyInfo Id="KeyId-1927847969"> <wsse:SecurityTokenReference xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="STRId-1543085802"> <wsse:Reference URI="#Cert467Id-26742559" ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"; /> </wsse:SecurityTokenReference> </ds:KeyInfo> </ds:Signature> </wsse:Security> <wsa:To>...</wsa:To> ... </wsa:MessageID> <wsa:Action>...</wsa:Action> </soapenv:Header> <soapenv:Body xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"; wsu:Id="Id-613975815"> <ns1:IssueTimestampToken xmlns:ns1="..."> <ns1:request> <ns1:ID>...</ns1:ID> <ns1:IssueInstant>...</ns1:IssueInstant> <ns1:Issuer>...</ns1:Issuer> <ns1:InputDocuments> <ns1:InputDocument> <ns1:Document> <ns1:Base64Data>...</ns1:Base64Data> </ns1:Document> </ns1:InputDocument> </ns1:InputDocuments> </ns1:request> </ns1:IssueTimestampToken> </soapenv:Body> </soapenv:Envelope> ------------------------------------------------------------------------------------ Regards, CBR600 Nunny wrote: > > Can you please post the captured message as well ? > > regards, > Nandana > > On Wed, Oct 14, 2009 at 8:10 AM, cbr600 > <[email protected]>wrote: > >> >> Hello, >> >> I am building a web service client using Metro and another one using Axis >> 2 >> with Rampart to talk to a .NET web service. The Metro client works fine >> but >> the Axis 2 does not. >> >> Following is the policy.xml (copied from the service WSDL) which I used >> for >> my Axis 2 - Rampart client: >> ... >> <sp:SignedParts >> xmlns:sp=" >> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";> >> <sp:Body /> >> <sp:Header Name="CoordinationContext" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2004/10/wscoor"; /> >> <sp:Header Name="CoordinationContext" >> Namespace=" >> http://docs.oasis-open.org/ws-tx/wscoor/2006/06"; /> >> <sp:Header Name="OleTxTransaction" >> Namespace=" >> http://schemas.microsoft.com/ws/2006/02/tx/oletx"; /> >> <sp:Header Name="IssuedTokens" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2005/02/trust"; /> >> <sp:Header Name="To" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2004/08/addressing"; /> >> <sp:Header Name="From" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2004/08/addressing"; /> >> <sp:Header Name="FaultTo" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2004/08/addressing"; /> >> <sp:Header Name="ReplyTo" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2004/08/addressing"; /> >> <sp:Header Name="MessageID" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2004/08/addressing"; /> >> <sp:Header Name="RelatesTo" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2004/08/addressing"; /> >> <sp:Header Name="Action" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2004/08/addressing"; /> >> </sp:SignedParts> >> <sp:EncryptedParts >> xmlns:sp=" >> http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";> >> <sp:Header Name="CoordinationContext" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2004/10/wscoor"; /> >> <sp:Header Name="CoordinationContext" >> Namespace=" >> http://docs.oasis-open.org/ws-tx/wscoor/2006/06"; /> >> <sp:Header Name="OleTxTransaction" >> Namespace=" >> http://schemas.microsoft.com/ws/2006/02/tx/oletx"; /> >> <sp:Header Name="IssuedTokens" >> Namespace=" >> http://schemas.xmlsoap.org/ws/2005/02/trust"; /> >> </sp:EncryptedParts> >> ... >> >> I looked at the Fiddler logs and Axis 2 - Rampart only signs the >> timestamp >> and the body of the request message. I wonder if this is a bug? >> >> Regards, >> CBR600 >> -- >> View this message in context: >> http://www.nabble.com/Axis-2---Rampart-does-not-sign-correctly-tp25885853p25885853.html >> Sent from the Axis - User mailing list archive at Nabble.com. >> >> > > -- View this message in context: http://www.nabble.com/Axis-2---Rampart-does-not-sign-correctly-tp25885853p25886459.html Sent from the Axis - User mailing list archive at Nabble.com.
