Hi Vinay, IntiatorSignatureToken is not currently supported. If you want to provider a patch I suggest looking at how the AsymmetricBindingBuilder builds the AsymmetricBinding policy model - it should be easy enough to add support for InitiatorSignatureToken here. The trickier task will be to add support to the AsymmetricBindingHandler to use this policy.
Colm. On Mon, Nov 14, 2011 at 7:21 PM, Penmatsa, Vinay <[email protected]> wrote: > I'm running CXF 2.4.1. > I do not see implementation or builder for IntiatorSignatureToken. Should I > do it myself? > > -Vinay > > > -----Original Message----- > From: Penmatsa, Vinay [mailto:[email protected]] > Sent: Monday, November 14, 2011 2:07 PM > To: [email protected] > Subject: InitiatorSignatureToken > > Hi, > A service that I need to use has the following policy definition: > <sp:AsymmetricBinding > xmlns:sp="http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702";> > <wsp:Policy> > <sp:InitiatorSignatureToken> > <wsp:Policy> > <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:InitiatorSignatureToken> > .... > .... > </sp:AsymmetricBinding> > > CXF could not process because it seems it didn't expect > "InitiatorSignatureToken" element. > I get the warning: > org.apache.cxf.ws.policy.AssertionBuilderRegistryImpl > handleNoRegisteredBuilder > WARNING: No assertion builder for type > {http://docs.oasis-open.org/ws-sx/ws-securitypolicy/200702}InitiatorSignatureToken > registered. > > Is this wrong policy definition or CXF limitation? or did I miss something? > > Regards, > Vinay > > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
