Hi,
I have set the timeToleranceInSeconds value to 24 hours in the client
application config file as well as on the Web Server that is running the Web
Service.
<microsoft.web.services2>
<diagnostics />
<security>
<timeToleranceInSeconds>86400</timeToleranceInSeconds>
</security>
</microsoft.web.services2>
To test this functionality, I changed the time of two client machines to
have a difference of 1 hour from the server. The first machine (which has WSE
2.0, SP3 - developer install) works fine, even with a 1 hour time difference
between the client and server. The second machine (which has WSE 2.0, SP3 -
runtime install) does not work with time difference of 1 hour (in fact, any
difference more than 5 mins). Any suggestions?
Thanks.
DW - 02 Jul 2005 00:39 GMT
Did you ever figure out why timeToleranceInSeconds has no effect on the
runtime? I'm seeing this same problem.
> Hi,
>
[quoted text clipped - 17 lines]
>
> Thanks.
delly_jm - 28 Sep 2005 17:46 GMT
Guys,
There's something I tried and it seemed to work.
Dim objMsgSign As MessageSignature = New
MessageSignature(objUserNameToken)
objWS.RequestSoapContext.Security.Timestamp.TtlInSeconds = 0
objWS.RequestSoapContext.Security.Tokens.Add(objUserNameToken)
objMsgSign.SignatureOptions = SignatureOptions.IncludeSoapBody
objMsgSign.SignatureOptions = Not
SignatureOptions.IncludeTimestamp
Try and see.
Delton
> Did you ever figure out why timeToleranceInSeconds has no effect on the
> runtime? I'm seeing this same problem.
[quoted text clipped - 20 lines]
> >
> > Thanks.
delly_jm - 28 Sep 2005 17:57 GMT
Hi guys, i tried this.
Dim objMsgSign As MessageSignature = New
MessageSignature(objUserNameToken)
objWS.RequestSoapContext.Security.Timestamp.TtlInSeconds = 0
objWS.RequestSoapContext.Security.Tokens.Add(objUserNameToken)
objMsgSign.SignatureOptions = SignatureOptions.IncludeSoapBody
objMsgSign.SignatureOptions = Not
SignatureOptions.IncludeTimestamp
Delton
http://www.particularpresence.com
> Hi,
>
[quoted text clipped - 17 lines]
>
> Thanks.