Created[1]. I added it as axis2 JIRA issue. May be I should've added it to the WSS4J jira space since its a more of a generic problem? Move it if I have placed it the wrong box http://issues.apache.org/jira/browse/AXIS2-1965 <http://issues.apache.org/jira/browse/AXIS2-1965> Thanks! George
________________________________ From: Ruchith Fernando [mailto:[EMAIL PROTECTED] Sent: Sat 1/6/2007 8:09 PM To: [email protected] Subject: Re: refering to tokens in rampart sec header Please file a JIRA. Thanks, Ruchith On 1/6/07, George Stanchev <[EMAIL PROTECTED]> wrote: > Thanks Ruchith, > > Do you need a JIRA opened for this enhancement to keep track or > you already have it on the list? > > > Best Regards, > George > > -----Original Message----- > From: Ruchith Fernando [mailto:[EMAIL PROTECTED] > Sent: Wednesday, January 03, 2007 5:01 AM > To: [email protected] > Subject: Re: refering to tokens in rampart sec header > > Hi, > > On 12/20/06, George Stanchev <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I need to create a securty token (saml, username) and refer to it from > > > the message body via wsse:SecurtyTokenReference. I am thinking that > > this is impossible using rampart since at the time when the payload is > > > created the token is not present and when the token gets created, > > there is no control to the client. > > Am I correct in my assumption? > > Yes! This is correct. > > > > > Are there alternatives besides creating the token manually and > > stuffing it in the sec header prior to calling sending the call on its > > > way? > > We don't haev an alternative right now and I believe this will be a > useful feature with the WS-Trust use cases. > We have to come up with a clean mechanism to do this where we can > specify a token to be added to the security header and to be used for > other purposes such as authentication or crypto operations. > > Thanks, > Ruchith > > > > > Thanks! > > > > George Stanchev > > > > > > ********************************************************************** > > This email and any files transmitted with it are confidential and > > intended solely for the use of the individual or entity to whom they > > are addressed. Any unauthorized review, use, disclosure or > distribution is prohibited. If you are not the intended recipient, > please contact the sender by reply e-mail and destroy all copies of the > original message. > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > www.ruchith.org > www.wso2.org > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- www.ruchith.org www.wso2.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
<<winmail.dat>>
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
