You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fx-dev@ws.apache.org by Malinda Kaushalye <ka...@cse.mrt.ac.lk> on 2004/06/18 05:15:17 UTC

Fw: [WSS4J] Implementing HMAC-SHA1 in WSS4J

----- Original Message -----
From: "Dimuthu Leelarathne." <mu...@opensource.lk>
To: <ka...@cse.mrt.ac.lk>
Sent: Friday, June 18, 2004 8:32 AM
Subject: Fw: [WSS4J] Implementing HMAC-SHA1 in WSS4J


>
> ----- Original Message -----
> From: "Dimuthu Leelarathne." <mu...@opensource.lk>
> To: <fx...@ws.apache.org>
> Sent: Wednesday, June 16, 2004 1:59 PM
> Subject: Fw: [WSS4J] Implementing HMAC-SHA1 in WSS4J
>
>
> >
> > ----- Original Message -----
> > From: "Dimuthu Leelarathne." <mu...@opensource.lk>
> > To: <fx...@ws.apache.org>
> > Sent: Tuesday, June 15, 2004 1:38 PM
> > Subject: [WSS4J] Implementing HMAC-SHA1 in WSS4J
> >
> >
> > > Hi all,
> > >
> > > We have launched WS-Secure Conversation implementation, and it looks
> like
> > we
> > > need the HMAC-signature(with the namespace
> > > http://www.w3.org/2000/09/xmldsig#hmac-sha1) to sign using derived
keys
> > > (symmetric).
> > >
> > > It is my opinion that we can accommodate this in
> > > org.apache.ws.security.message.WSSignEnvelope as another method. This
is
> > > analogous to WSEncryptbody's, build and buildEmbedded methods.
> > >
> > > Should we go ahead and do it? Is there a better way of doing it?
> > >
> > > Thanks,
> > > Dimuthu.
> > >
> > >
> >