Hi All;
Following call did the trick, :)
OutflowConfiguration ofc = new OutflowConfiguration();
...............
ofc.setSignatureKeyIdentifier("DirectReference");
Thanks
Srinath
On 12/28/05, Srinath Perera <[EMAIL PROTECTED]> wrote:
> Hi All;
>
> I use wss4j with Axis2 client (Axis2 security modules ) to sign a
> message, in the request Message the key info do not use
> BinarySecurityToken. The Message is something like this
>
> <ds:KeyInfo Id="KeyId-3190337">
> <wsse:SecurityTokenReference wsu:Id="STRId-19697576">
> <ds:X509Data>
> <ds:X509IssuerSerial>
> <ds:X509IssuerName>....</ds:X509IssuerName>
> <ds:X509SerialNumber>76</ds:X509SerialNumber>
> </ds:X509IssuerSerial>
> </ds:X509Data>
> </wsse:SecurityTokenReference>
> </ds:KeyInfo>
>
> But the server do not understand this and expect something like
>
> <ds:KeyInfo>
> <wsse:SecurityTokenReference>
> <wsse:Reference URI="#token1117575311345"/>
> </wsse:SecurityTokenReference>
> </ds:KeyInfo>
> <wsse:BinarySecurityToken > ...</wsse:BinarySecurityToken>
>
> Is there a way to configure wss4j to use BinarySecurityToken in the key info?
>
> Thanks
> Srinath
>
