No, the SupportingToken policies are message level policies and as such need to be configured using the WS-Security properties.
Colm. On Mon, Jan 22, 2018 at 3:06 PM, vlad.balan <vlad.ba...@gmail.com> wrote: > > Hello > > can a supportingToken of typpe X509Token like this one > > > > > > <sp:SupportingTokens > xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";> > <wsp:Policy> > <sp:UsernameToken > sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws- > securitypolicy/200702/IncludeToken/AlwaysToRecipient"> > <wsp:Policy> > <sp:WssUsernameToken11/> > </wsp:Policy> > </sp:UsernameToken> > <sp:X509Token > sp:IncludeToken="http://docs.oasis-open.org/ws-sx/ws- > securitypolicy/200702/IncludeToken/AlwaysToRecipient"> > <wsp:Policy> > <sp:WssX509V3Token10/> > </wsp:Policy> > </sp:X509Token> > </wsp:Policy> > </sp:SupportingTokens> > > > come from conduit tlsClientParameters element (maybe by alsi specifying the > transportBinding/httpsToken policy in extra) and not have to use client > properties > > > > <entry key="security.signature.properties" > value="security.signature.properties"/> > <entry key="security.encryption.properties" > value="security.encryption.properties"/> > > (in this case, it comes from the alias in security.signature.properties) > > Thanks. > > > > -- > Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
