JDeveloper WS Security Client Proxy - Axis WS

Question

Hi everybody
i'm using JDeveloper 10.1.3.3.0.
I'm trying to connect to a webservice developed by a external provider. The external provider used axis (i dont know what is its version nor nothing about its configuration) to create the ws. When i test the ws client proxy, the ws developed in axis returns the following fault:
javax.xml.rpc.soap.SOAPFaultException: WSDoAllReceiver: security processing failed (actions mismatch)
     at oracle.j2ee.ws.client.StreamingSender._raiseFault(StreamingSender.java:555)
     at oracle.j2ee.ws.client.StreamingSender._sendImpl(StreamingSender.java:396)
     at oracle.j2ee.ws.client.StreamingSender._send(StreamingSender.java:112)
Reading the axis documentation, i found that the problem could be the order and the quantity of the ws security header elements. In my case, i'm trying with only the Signature and Timestamp elements (In that order). The external provider told me that those are the actions expected by them. So, the logical alternative than probably solve this problem is to switch the order of the ws security header elementes (Firts Timestamp, then Signature).
I created the ws proxy using the jdeveloper wizard. Then, i modified the xxxSoapBinding_Stub.xml like this:
<oracle-webservice-clients xmlns:....
<runtime enabled="security">
<security>
<key-store name="myks" path="c:/temp/cert/myks.jks" store-pass="password"/>
<signature-key alias="test" key-pass="password"/>
<encryption-key alias="test" key-pass="password"/>
<inbound/>
<outbound>
<signature>
<signature-method>RSA-SHA1</signature-method>
<tbs-elements>
<tbs-element local-part="Body" name-space="http://schemas.xmlsoap.org/soap/envelope/"/>
</tbs-elements>
<add-timestamp created="true" expiry="28800" />
</signature>
</outbound>
</security>
</runtime>
<operations>
<operation name="queryDeclarations">
</operation>
</operations>
</port-info>
</webservice-client>
</oracle-webservice-clients>
This is the ws security header generated by my proxy client in this moment:
<wsse:Security
     xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
     xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
     xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"
     env:mustUnderstand="1">
     <wsse:BinarySecurityToken
          xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
          xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
          ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3"
          EncodingType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-soap-message-security-1.0#Base64Binary"
          wsu:Id="_6F60NR6IXB2dYJCgIYy9JA22"
          xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
          MIIGLzCCBRegAwIBAg...
     </wsse:BinarySecurityToken>
     <dsig:Signature xmlns="http://www.w3.org/2000/09/xmldsig#"
          xmlns:dsig="http://www.w3.org/2000/09/xmldsig#">
          <dsig:SignedInfo>
               <dsig:CanonicalizationMethod
                    Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
               <dsig:SignatureMethod
                    Algorithm="http://www.w3.org/2000/09/xmldsig#rsa-sha1" />
               <dsig:Reference URI="#MOmq8nF2iGaNEXc4TEN0ew22">
                    <dsig:Transforms>
                         <dsig:Transform
                              Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#" />
                    </dsig:Transforms>
                    <dsig:DigestMethod
                         Algorithm="http://www.w3.org/2000/09/xmldsig#sha1" />
                    <dsig:DigestValue>
                         ExIbc9ws2rIxB4j8DD64y3kjSoA=
                    </dsig:DigestValue>
               </dsig:Reference>
          </dsig:SignedInfo>
          <dsig:SignatureValue>
               ieZtnbn2ytnmyE8fL9lO10nwzYARHu...
          </dsig:SignatureValue>
          <dsig:KeyInfo>
               <wsse:SecurityTokenReference
                    xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
                    xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd">
                    <wsse:Reference
                         xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
                         xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd"
                         URI="#_6F60NR6IXB2dYJCgIYy9JA22"
                         ValueType="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-x509-token-profile-1.0#X509v3" />
               </wsse:SecurityTokenReference>
          </dsig:KeyInfo>
     </dsig:Signature>
     <wsu:Timestamp
          xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd"
          xmlns="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd">
          <wsu:Created>2010-04-29T23:17:38Z</wsu:Created>
          <wsu:Expires>2010-04-30T07:17:38Z</wsu:Expires>
     </wsu:Timestamp>
</wsse:Security>
is there any way to switch the ws security header elements using jdeveloper or does exist some diferent thing that i can do?
I try using Handlers to capture the SOAPMessage object with the request before it were send. But, on that moment the ws security headers are not present yet in the request. It seems that the request is proceced later behind the scenes :(.... maybe far away from my develpment workspace scope :).
Anyone has tried to do something like i trying to do??
any suggestion?
Thanks in advance
Javier Murcia

Answer 1

I thought you were getting that exception when accessing the proxy.
No. Authentification works fine. Proxy body works fine. But at the end of proxy appears the exception.
Sorry for my english - I tried to show this situation on image: http://imglink.ru/show-image.php?id=9c0e0c1719f00289faf11696c6703bc3
Are you getting this exception when routing to a business service which is configured for WS-Security ??
I don't use business service in this test project - only simple proxy service with all logic inside.
PS transformation in replace action is very simple too:
(:: pragma bea:global-element-parameter parameter="$newOperation1" element="ns0:NewOperation" location="WSSecurityService.wsdl" ::)
(:: pragma bea:global-element-return element="ns0:NewOperationResponse" location="WSSecurityService.wsdl" ::)
declare namespace ns0 = "http://www.troika.ru/Enterprise/WSSecurityService/";
declare namespace xf = "http://tempuri.org/OSB%20Project%20WS-Security/Hello/";
declare function xf:Hello($newOperation1 as element(ns0:NewOperation))
as element(ns0:NewOperationResponse) {
<ns0:NewOperationResponse>
<out>Hello, { data($newOperation1/in) }!</out>
</ns0:NewOperationResponse>
declare variable $newOperation1 as element(ns0:NewOperation) external;
xf:Hello($newOperation1)
Edited by: Andrey L. on Jun 10, 2010 12:21 PM