Consuming Web Service (WS-Security enabled) from a client not supporting WS-Security specs

Hi Ruwan,

Thanks for your quick reply. I'll give it a try.

Regards,
Alexandre

 I followed the sample 100 that is much more complex that I need. I tried to adapt it accordingly to my requirements but I get stuck on a blocking issue.

To refresh your mind, the scenario is quite simple : consumer -> esb -> web service. The ESB is responsible to deal with WS-Security elements (usernameToken and Timestamp).

Proxy Service Conf

<syn:proxy name="MyProxy" transports="https http" startOnLoad="true">
  <syn:target>
    <syn:inSequence>
      <syn:send>
        <syn:endpoint>
          <syn:address uri="http://localhost:9001/soap/MyService">
            <syn:enableAddressing/>
            <syn:enableSec policy="policy.my-proxy"/>
          </syn:address>
        </syn:endpoint>
      </syn:send>
    </syn:inSequence>
    <syn:outSequence>
      <syn:send/>
    </syn:outSequence>
  </syn:target>
  <syn:publishWSDL uri="http://localhost:9001/soap/MyService?wsdl"/>
</syn:proxy>

Related Policy File

<wsp:Policy wsu:Id="usernametoken-timestamp" 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:TransportBinding xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
      <wsp:Policy>
        <sp:TransportToken>
          <wsp:Policy>
            <sp:HttpsToken RequireClientCertificate="false"/>
          </wsp:Policy>
        </sp:TransportToken>
        <sp:AlgorithmSuite>
          <wsp:Policy>
            <sp:Basic256/>
          </wsp:Policy>
        </sp:AlgorithmSuite>
        <sp:Layout>
          <wsp:Policy>
            <sp:Lax/>
          </wsp:Policy>
        </sp:Layout>
        <sp:IncludeTimestamp/>
      </wsp:Policy>
    </sp:TransportBinding>
    <sp:SignedSupportingTokens xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy">
      <wsp:Policy>
        <sp:UsernameToken sp:IncludeToken="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy/IncludeToken/AlwaysToRecipient" />
      </wsp:Policy>
    </sp:SignedSupportingTokens>
    <ramp:RampartConfig xmlns:ramp="http://ws.apache.org/rampart/policy"> 
      <ramp:user>xxxx</ramp:user>
      <ramp:passwordCallbackClass>xxx.xxxxxxxx.PWHandlerClient</ramp:passwordCallbackClass>
    </ramp:RampartConfig>
  </wsp:All>
</wsp:ExactlyOne>
</wsp:Policy>

The ESB sends the password in plain text whereas the web service expects a digest password type.

Message Sent by the ESB

<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="UsernameToken-32014774">
    <wsse:Username>xxxx</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordText">xxxx</wsse:Password>
</wsse:UsernameToken>

Message expected by the Web Service

<wsse:UsernameToken xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-utility-1.0.xsd" wsu:Id="UsernameToken-12227392">
    <wsse:Username>xxxx</wsse:Username>
    <wsse:Password Type="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-username-token-profile-1.0#PasswordDigest">f5pT0iffQf0P5/5RiOqR7d4aVus=</wsse:Password>
    <wsse:Nonce>QHP4sKdYXyhllXyIswS6+w==</wsse:Nonce>
    <wsu:Created>2008-03-27T15:04:58.150Z</wsu:Created>
</wsse:UsernameToken>

What is the proper configuration enabling the ESB to send the password in the digest format?

Any pointer to the documentation will be appreciated,

Regards,
Alexandre