Simon, I have the same sort of problem (sort of) in that while the first server I'm talking to as a client requires the security, the second (back end) server doesn't understand it.
You can see this thread - http://www.nabble.com/Rampart-1.4-mustUnderstand-td19926442.html http://www.nabble.com/Rampart-1.4-mustUnderstand-td19926442.html To finally get this to work, we had to modify the source code for ramart just for our installation. Basically manually setting it in the RampartMessageData class: this.secHeader = new WSSecHeader(); secHeader.setMustUnderstand(false); // inserted Not at all attractive, but it worked... good for a one off solution I guess. Simon-2716 wrote: > > Hello, > > > > I am sending a usernametoken and automatically the mustUnderstand > attribute > is set to true in the Secuirty header. My counterpart service does > understand security headers, but somehow an exception is thrown, that the > mustunderstand check failed. Is it possible to tell my client to NOT add > the > mustUnderstand="true" attribute? > > > > Thanks for your help, > > Regards Simon > > > > > -- View this message in context: http://www.nabble.com/Rampart%2C-turning-off-mustUnderstand%3D%22true%22-in-Header-tp20113579p20116281.html Sent from the Axis - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
