At least one timestamp expire.

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

syed javid - 05 Dec 2004 11:53 GMT

Hi All,

I am having a WSE 2.0 webservice that authenticate X509 client and
client to send x509 token for authentication.
The x509 authentication work fine when it is used from intranet
but it fails when the client sends x509 token from internet.
i am using trusted x509 certificate

The following is the error message:
At least one timestamp expire.

Any help

javid
KSA

Reply to this Message

nealboy - 05 Dec 2004 17:26 GMT

The Web Services sever on Internet may clock asynchronizate to your
client.If you can't make clockes of both computer synchronzated,you can set
time-to-live (TTL) for the SOAP message to solve this problems in following
code:
YourProxy.RequestSoapContext.Security.Timestamp.TtlInSeconds =-1 'never
expire
or
YourProxy.RequestSoapContext.Security.Timestamp.TtlInSeconds =enough
number of seconds

Hope it's help.

nealboy

> Hi All,
>
[quoted text clipped - 11 lines]
> javid
> KSA

Reply to this Message

syed javid - 07 Dec 2004 11:29 GMT

hi nealboy,
Thanks for reply,
I tried by setting TtlInSeconds = -1 at the client side, but still have the
same problem.
Do you have any more suggestions

> The Web Services sever on Internet may clock asynchronizate to your
> client.If you can't make clockes of both computer synchronzated,you can set
[quoted text clipped - 24 lines]
> > javid
> > KSA

Reply to this Message

Dan Rogers - 07 Dec 2004 20:21 GMT

What timezones are involved?

--------------------
Thread-Topic: At least one timestamp expire.
thread-index: AcTcT/lQvefAxqL+RJyc410NtO1nMA==
X-WBNR-Posting-Host: 212.138.47.13
From: "=?Utf-8?B?c3llZCBqYXZpZA==?=" <syedjavid@discussions.microsoft.com>
References: <EFE228DF-C523-4FA3-AB3B-D02E9EC8EA64@microsoft.com>
<O2GFL#u2EHA.2180@TK2MSFTNGP10.phx.gbl>
Subject: Re: At least one timestamp expire.
Date: Tue, 7 Dec 2004 03:29:11 -0800
Lines: 48
Message-ID: <907A0FA9-5E15-4D4D-A393-F3FBB929F067@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices.enhancements
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA
03.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices.enhancements:5062
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices.enhancements

hi nealboy,
Thanks for reply,
I tried by setting TtlInSeconds = -1 at the client side, but still have
the
same problem.
Do you have any more suggestions

"nealboy" wrote:

> The Web Services sever on Internet may clock asynchronizate to your
> client.If you can't make clockes of both computer synchronzated,you can set
[quoted text clipped - 26 lines]
> > javid
> > KSA

Reply to this Message

syed javid - 08 Dec 2004 07:49 GMT

yes that 's the ans, there was a 3 minutes diff in time
It works when i set the same time at both the sides server/client machines.
Can't we ignore this

> What timezones are involved?
>
[quoted text clipped - 69 lines]
> > > javid
> > > KSA

Reply to this Message

Dan Rogers - 10 Dec 2004 18:40 GMT

I'm traveling right now... so I don't have the specifics at my finger tips.
There is a way to tell it to increase the difference that it cares about.
You can also just set the timeout on the message you send to -1 (infinity).
In general, I'd advise not shaving the timeout intervals so tight that
these types of things go wrong.

If you are using timeout to control/or manage the application level concept
of "throw this away as not relevant if too much time elapses", then I
wouldn't advise using the message infrastructure layer to do this (since it
causes an error, not an ignore). Now, granted, others will certainly
disagree with my perspective on this - but if it's application level
"ignore" you want, to me that's an application level decision.

--------------------
Thread-Topic: At least one timestamp expire.
thread-index: AcTc+mHJG0JIuh72R7aZuOAb8pFyow==
X-WBNR-Posting-Host: 212.138.47.20
From: "=?Utf-8?B?c3llZCBqYXZpZA==?=" <syedjavid@discussions.microsoft.com>
References: <EFE228DF-C523-4FA3-AB3B-D02E9EC8EA64@microsoft.com>
<O2GFL#u2EHA.2180@TK2MSFTNGP10.phx.gbl>
<907A0FA9-5E15-4D4D-A393-F3FBB929F067@microsoft.com>
<93NROpJ3EHA.1512@cpmsftngxa10.phx.gbl>
Subject: Re: At least one timestamp expire.
Date: Tue, 7 Dec 2004 23:49:01 -0800
Lines: 91
Message-ID: <79EB8614-135A-4496-B172-6DA71CF22CAD@microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 8bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.dotnet.framework.webservices.enhancements
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl
microsoft.public.dotnet.framework.webservices.enhancements:5083
X-Tomcat-NG: microsoft.public.dotnet.framework.webservices.enhancements

yes that 's the ans, there was a 3 minutes diff in time
It works when i set the same time at both the sides server/client machines.
Can't we ignore this

"Dan Rogers" wrote:

> What timezones are involved?
>
[quoted text clipped - 21 lines]
> NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
> Path:

cpmsftngxa10.phx.gbl!TK2MSFTFEED02.phx.gbl!TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA

> 03.phx.gbl
> Xref: cpmsftngxa10.phx.gbl
[quoted text clipped - 27 lines]
> > nealboy
> > "syed javid" <syedjavid@discussions.microsoft.com>

??????????????????"??? ????????

> > news:EFE228DF-C523-4FA3-AB3B-D02E9EC8EA64@microsoft.com...
> > > Hi All,
[quoted text clipped - 12 lines]
> > > javid
> > > KSA

Reply to this Message

At least one timestamp expire.

Free Magazines