Re: [WSS4J] client handler chaining with different actors

Yes,
could be a real bug :-). This "chaining was not very well tested (at least
not
with different actors). I need to update my source tree here and have a
look.
Appreciate if you can just send a patch or something like that :-).

Regards,
Werner

----- Original Message -----
From: "Yves Langisch" <lists-iO7QwSo9/2sfv37vnLkPlQ@xxxxxxxxxxxxxxxx>
To: <fx-dev-28n8OjmUYWfNLxjTenLetw@xxxxxxxxxxxxxxxx>
Sent: Wednesday, August 25, 2004 6:58 PM
Subject: [WSS4J] client handler chaining with different actors


> All,
>
> On client-side I use a handler chain with following actions:
>
> handler1 = Timestamp Signature NoSerialization
> handler2 = Encrypt
>
> For both of them I define a different actor in order to get TWO security
> headers but the message on the wire always contains only one header
> (with actor=handler2actor) with all the information (ts, sig, enc) in
> it. I looked through the source and found the location where this
> 'overwriting' or 'merging' happens: The method insertSecurityHeader in
> the WSBaseMessage class seems to be 'actor-aware'. But inside of this
> method there is a call to WSSecurityUtil.findWsseSecurityHeaderBlock
> which should add oder supplement a header for a specific actor. But if
> there is already a security header it always returns this one instead of
> creating a new one if the actor differs.
>
> Am I understanding anything wrong or is this a bug?
>
> Regards,
> Yves
>
> PS. I'm using the latest source.