Hi,
I'm not sure if you can't disable the timestamp validation at all, but these
settings might help you:
<!--
The defaultTtlInSeconds section defines a user supplied time-to-live for
every outgoing message.
It is optional, and its default value is 5 minutes.
SoapContext.Security.Timestamp.TtlInSeconds is used
to set a time-to-live for some particular message.
<defaultTtlInSeconds>insert a default time-to-live for the every
message</defaultTtlInSeconds>
-->
<!--
The timeToleranceInSeconds section defines a user supplied time buffer when
WSE is comparing
current time against creation time for post dated and expiration time for
past time. It is usually
the time skew between client and server machine. Default is five minutes.
<timeToleranceInSeconds>insert the time tolerance for timestamp
checking</timeToleranceInSeconds>
-->
Regards,
Pablo Cibraro
http://weblogs.asp.net/cibrax
http://www.lagash.com
> Dear:
> I use wse2.0 to establish a system.When the client time is different
> with the server,the client can't communicate with the server and make
> error
> that created timestamp is in the future.I want to know how I can make soap
> message without timestamp.
GCR - 08 Dec 2005 14:50 GMT
That's not really the point, since the WS-security specification relies on
the timestamp! You could create a custom security object, inheriting from the
Microsoft.Web.Security.Security object, but it wouldn't conform with the
WS-Security specification anymore.
But I would recomend synchronising your computer with a public ntp server
and setting the Created and Expires properties programatically.
> Hi,
> I'm not sure if you can't disable the timestamp validation at all, but these
[quoted text clipped - 33 lines]
> > that created timestamp is in the future.I want to know how I can make soap
> > message without timestamp.