One Star

Authenticating with UsernameToken and Password Digest

Hi All,
I am working with Talend ESB version 5.6.1 - as part of a mediation route, I am making a call out to another SOAP web service using a cCXF component. This producer service requires authentication in the form of username tokens with a password digest.
I have checked the box 'Use Authentication' in the component and selected the type as 'UsernameToken' and added the username and password that I have been given to access the service. When I make the web service call, the SOAP headers are being updated with the username and password, but the password is being supplied as 'PasswordText':
<SOAP-ENV:Header xmlnsSmiley FrustratedOAP-ENV="">
<wsseSmiley Frustratedecurity
 xmlns:wsse="" xmlns:wsu="" soap:mustUnderstand="1">
<wsseSmiley Tongueassword
 Type="">***PlainText Password ***</wsseSmiley Tongueassword>
</wsseSmiley Frustratedecurity>

However, I need to be able to specify the password with a type of 'PasswordDigest' which will subsequently hash the password with the nonce and timestamp:
  <soapenv:Header xmlns:wsa="">

<wsseSmiley Frustratedecurity soapenv:mustUnderstand="1" xmlns:wsse=""xmlns:wsu="">
        <wsse:UsernameToken wsu:Id="UsernameToken-3A6A283FDF95E3B9F814776448761251">
           <wsseSmiley Tongueassword Type="">
NE+xXdqCKXvYDeIPCGvqOt4KaYq=</wsseSmiley Tongueassword>

           <wsse:Nonce EncodingType="">
     </wsseSmiley Frustratedecurity>

Has anyone been able to authenticate as the client to another web service using username tokens with a type of PasswordDigest?

Many thanks,


Re: Authenticating with UsernameToken and Password Digest

Hi Sam,
Right now, we don't support creating UsernameTokens with digest passwords in the Studio. I've created a JIRA in the past for this feature here:
I experimented with cProcessor to add the UsernameToken manually, however I wasn't able to get it to work in PAYLOAD mode, as the generated code turns off relay headers. It should be possible though to get it to work for non-PAYLOAD modes if this is an option for you.
Alternatively, it's possible to get it to work when you deploy to the container (but not in the Studio). If you select the UsernameToken authentication in the Studio + then deploy the route to the container, it uses the policy stored in etc/org.talend.esb.job.token.policy to create the security header. If you change the policy to for example:
 <sp:UsernameToken sp:IncludeToken="">
                <wspSmiley Tongueolicy>
                </wspSmiley Tongueolicy>
Then it will create a UsernameToken with a hashed password.