Re: multiple entries in soap security header for Signature, Timestamp, EncryptedKey

[pra...@tracelink.com]

Should the wsdl basically look like this?

<wsp:Policy wsu:Id="CustomBinding_IProductServiceMahV20161_policy">
  <wsp:ExactlyOne> 
     <wsp:All> 
         <sp:AsymmetricBinding
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>...
         </sp:AsymmetricBinding>
         <sp:SignedSupportingTokens
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>...
         </sp:SignedSupportingTokens>
        <sp:Wss11
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>...</sp:Wss11>
        <sp:Trust10
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>...</sp:Trust10>
       <wsaw:UsingAddressing/>
    </wsp:All>
     <wsp:All> 
         <sp:SignedSupportingTokens
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>...
         </sp:SignedSupportingTokens>
        <sp:Wss11
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>...</sp:Wss11>
        <sp:Trust10
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>...</sp:Trust10>
        <sp:TransportBinding
xmlns:sp="http://schemas.xmlsoap.org/ws/2005/07/securitypolicy";>...
        </sp:TransportBinding>
        <wsaw:UsingAddressing/>
    </wsp:All>
  </wsp:ExactlyOne>
</wsp:Policy>


I split the <AsymmetricBinding> and <TransportBinding> into its own <All>
and kept the rest the same. Let me know if this is valid and I will try this
out. 

*Question:*
A side question, if I'm unable to get the wsdl changed (because I don't
control the wsdl), then will the multiple entries for Signature, Timestamp
etc in the soap security header cause issues?



--
Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html