Hi,
This is a known, documented and outstanding issue with SP1.
Regards
Dan Rogers
Microsoft Corporation
--------------------
From: Robbert van Geldrop via .NET 247 <anonymous@dotnet247.com>
X-Newsreader: AspNNTP 1.50 (Matthew Reynolds Consulting)
Subject: Time Tolerance does not work 'backwards in time'
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Message-ID: <OePXvGI6EHA.824@TK2MSFTNGP11.phx.gbl>
Newsgroups: microsoft.public.dotnet.framework.webservices.enhancements
Date: Wed, 22 Dec 2004 15:55:14 -0800
NNTP-Posting-Host: 81-86-69-114.dsl.pipex.com 81.86.69.114
Lines: 1
Path:
cpmsftngxa10.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11
.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices.enhancements:5241
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices.enhancements
Hello,
I have a web service that runs on WSE2.0 sp1 with the following relevant
settings:
- Default ttl in seconds = -1
- Time tolerance in seconds = 43200
I am testing a client with WSE2.0 and I noticed that if I set:
- Time tolerance in seconds = 43200 by putting in app.config:
<configSections>
<section name="microsoft.web.services2"
type="Microsoft.Web.Services2.Configuration.WebServicesConfiguration,
Microsoft.Web.Services2, Version=2.0.0.0, Culture=neutral,
PublicKeyToken=31bf3856ad364e35" />
</configSections>
<microsoft.web.services2>
<security>
<timeToleranceInSeconds>43200</timeToleranceInSeconds>
</security>
<diagnostics />
</microsoft.web.services2>
and in the code calling the webService:
object.RequestSoapContext.Security.Timestamp.TtlInSeconds = -1
When I have a client that is in a time zone (e.g. +5 GMT) later than my web
service (+1 GMT) then it works perfectly, but when my client is earlier
(e.g. -3 GMT) I get an error:
"Creation time in the timestamp can not be in the future."
Is this a known bug or do I have to set more configuration settings on the
client/server side?
--------------------------------
From: Robbert van Geldrop
-----------------------
Posted by a user from .NET 247 (
http://www.dotnet247.com/)
