RE: [wss] interop scenario 1:3 -> timestamp

["Hal Lockhart" <hlockhar@bea.com>]

As far as I can remember, this is an out and out bug. I agree that it is wrong and should be in the security header. I am surprised nobody caught it before. As I recall, I was trying to stimulate discussion by proposing that we ignore the timestamp. (There had been extensive discussion about the semantics of timestamps, especially the expires attribute.)

I am still waiting for OASIS to set up the mailing lists for the interop, so we can discuss issues like this. Once we agree on some scenarios, I will produce a new docuemtn for this event.

Hal

> -----Original Message-----
> From: Granqvist, Hans [mailto:hgranqvist@verisign.com]
> Sent: Tuesday, March 01, 2005 6:12 PM
> To: Hal Lockhart; Granqvist, Hans; Kelvin Lawrence;
> wss@lists.oasis-open.org
> Subject: [wss] interop scenario 1:3 -> timestamp
> 
> 
> 
> Interop 1, scenario 3 has a wsu:Timestamp outside the wsse:Security 
> header (interop doc, line 508). 
> 
> The spec defines a Timestamp as child of Security (1.0 spec, line 
> 1297), but the Timestamp in the above interop scenario is outside 
> the Security element. 
> 
> Though the interop processing rules (line 483) say the Timestamp 
> element must be ignored. 
> 
> This makes me wonder why the Timestamp is in the interop 
> scenario: Was 
> the intention that the timestamp should be in the Security header and 
> not in the Soap header?  (It's a bit confusing if the interop "reaches
> out" of the Security header like this.)
> 
> 
> 
> > -----Original Message-----
> > From: Hal Lockhart [mailto:hlockhar@bea.com] 
> > Sent: Wednesday, February 09, 2005 2:04 PM
> > To: Granqvist, Hans; Kelvin Lawrence; wss@lists.oasis-open.org
> > Subject: RE: [wss] Interop demo opportunity at Gartner, April 20th
> > 
> > 
> > I just uploaded the Interop 1 & 2 specs to the Scenarios and 
> > Test Cases folders. There may be a few minor changes which 
> > were made after these were published, but they should let you 
> > know what we are talking about.
> > 
> > Hal
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wss-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wss-help@lists.oasis-open.org
> 
>