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/16 12:08:08 UTC

Fw: [Patch] A proposal to accomodate WS-SecureConversation Implementation

FYI:
Dimuthu tried to mail this to the mailing list.
But It doesn't seems to get there.
----- Original Message -----
From: "Dimuthu Leelarathne." <mu...@opensource.lk>
To: <fx...@ws.apache.org>
Cc: <ru...@cse.mrt.ac.lk>; <ch...@virtusa.com>;
<sa...@opensource.lk>; <ka...@cse.mrt.ac.lk>; <mu...@cse.mrt.ac.lk>
Sent: Wednesday, June 16, 2004 2:01 PM
Subject: Fw: [Patch] A proposal to accomodate WS-SecureConversation
Implementation


>
> ----- Original Message -----
> From: "Dimuthu Leelarathne." <mu...@opensource.lk>
> To: <fx...@ws.apache.org>
> Sent: Tuesday, June 15, 2004 1:50 PM
> Subject: [Patch] A proposal to accomodate WS-SecureConversation
> Implementation
>
>
> > Hi All,
> >
> > I created this parch due to couple of reasons and we are hoping to get
the
> > green light to go ahead and commit it :-).
> >
> > Reason 1:
> > WS Secure conversation handlers are using WSEncryptbody for encryption,
> and
> > they need to get symmetric key that is used in the following method
(line
> > number 531)
> >  public Document build(Document doc, Crypto crypto) throws
> > WSSecurityException
> >
> > Reason 2:
> > We need the <EncryptedKey> as a child element of RequestedProofToken
> > element. So we need to be able to set the parentNode into which
> EncryptedKey
> > element should be inserted.
> >   <wsse:RequestedProofToken>
> >          <xenc:EncryptedKey>
> > .............
> >        </xenc:EncryptedKey>
> >    </wsse:RequestedProofToken>
> >
> >
> > Thanks,
> > Dimuthu.
> >
> >
> >
>