Hi Brecht, Why not just use the standard approach of associating a security binding with the WSDL binding, and then associate a SignedParts policy with the WSDL input, but no (SignedParts) policy with the WSDL output? I just checked doing this in a system test and it worked fine.
Colm. On Mon, Aug 3, 2015 at 3:52 PM, Brecht Yperman <[email protected]> wrote: > Hi, > I already posted this to Stackoverflow, but I'm guessing I'll get better > responses here. > > I'm addressing a webservice using CXF that requires a WS-Security > Signature on the request, but the response has no signature. I recently > moved from Axis2 to CXF, but would try to keep all existing configuration > working as much as possible. > In Axis2 I was able to specify a different policy for the request and the > response. > client.getOptions().setProperty(RampartMessageData.KEY_RAMPART_OUT_POLICY, > outPolicy); > > I tried setting a different policy for the request context and the > response context, but that seems to have no effect (the policy is found on > the Exchange, which has all properties copied from the requestContext in > the ClientImpl.doInvoke method) > client.getRequestContext().put(PolicyConstants.POLICY_OVERRIDE, > outPolicy); > > Is this possible using Apache CXF? > Thanks, > Brecht > > [http://www.invenso.com/emailimgs/Invenso.png] > > - > > ________________________________ > > - > > - > > Brecht Yperman > Senior Developer > E [email protected]<mailto:[email protected]> > P +32 52 52 27 75 > > [http://www.invenso.com/emailimgs/xd.png]<http://www.xperido.com/> > > XperiDo<http://www.xperido.com> > Document creation & output management > > [http://www.invenso.com/emailimgs/xb.png]<http://www.xbintegrator.com/> > > XBintegrator<http://www.xbintegrator.com> > Integration & development foundation > > - > > ________________________________ > > - > > > > - > > The contents of this e-mail and any of its attachments are intended for > work preparation purposes only, and do by no means contain any legally > binding promises or statements. They are intended only for use by the > addressee(s) named herein and may contain legally privileged and/or > confidential information. If you are not the intended recipient, please > note that any review, dissemination, disclosure, alteration, printing, > copying or transmission of this e-mail and/or any file transmitted with it, > is strictly prohibited and may be unlawful. If you have received this > e-mail by mistake, please immediately notify the sender and permanently > delete the original as well as any copy of any e-mail and any printout > thereof. > > > -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
