HI, I'm not creating the message without EncodingType, the service that I'm calling is doing that. Unfortunately I have no control over that service, that is why I have to work around it.
I assume that I can set this property in the WSS4JInterceptor, but how can i set just this property without having to configure everything by hand? kind regards, Ted 2013/8/14 Colm O hEigeartaigh <[email protected]> > The EncodingType is mandatory according to the Basic Security Profile > specification. You can disable validation of an incoming message against > this specification by setting the property "ws-security.is-bsp-compliant" > to "false". See here for more details: > > http://cxf.apache.org/docs/ws-securitypolicy.html > > How are you creating the message that it is not putting in an > "EncodingType"? Could you attach your configuration + the resulting > message? > > Colm. > > > On Wed, Aug 14, 2013 at 10:42 AM, Ted Roeloffzen > <[email protected]>wrote: > > > Hi All, > > > > I'm still trying to figure out CXF and WSSE. > > At this point, sending a message to the server works fine, aside from the > > timestamp not being correct. > > But the return message gives a exception. > > I get the exception that there is no EncodingType, or at least it says > that > > the EncodingType is "". > > When I look at the message I'm getting there is no EncodingType in the > > BinarySecurityToken-element. Is it mandatory for CXF to have an > > EncodingType here? > > > > If so, how can I programmaticaly alter the WSSE-securityheader and insert > > this property? > > > > kind regards, > > > > Ted > > > > > > -- > Colm O hEigeartaigh > > Talend Community Coder > http://coders.talend.com >
