Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
HomeAnnouncementsFree MagazinesWhite PapersSubmit Content
Discussion GroupsASP.NETWindows FormsLanguages.NET FrameworkVisual Studio.NET
Articles.NET FrameworkASP.NETToolsWindows Forms
.NET DirectoryOpen Source ProjectsUser GroupsWeb Resources
Related Topics
Visual Basic 6SQL ServerMS AccessOther DB ProductsMS Server ProductsMore Topics ...

.NET Forum / ASP.NET / Web Services / November 2006

Tip: Looking for answers? Try searching our database.

WSE 3.0 and timeToleranceInSeconds element

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Sergey Pikhulya - 28 Jun 2006 14:41 GMT
Documentation about <timeToleranceInSeconds> Element says:

"Use the <timeToleranceInSeconds> element when there is a clock difference
between the SOAP message sender and receiver.WSE invalidates SOAP messages
that have expired or are created in the future during its message validation
phase. That is, during message validation, WSE verifies that the value of
the <Created> element within the timestamp is in the past and that the
<Expires> element of the timestamp is in the future. When there is a
difference between the two clocks such that the sender's clock is ahead of
the receiver's clock, the <Created> element within the timestamp might be in
the future in relation to the receiver's clock. In that scenario, WSE would
reject the SOAP message during its validation phase. ...

... The minimum value is 0 and the maximum value is 86400 (24 hours). ... "

But I need significantly more value of maximum, ideally it should not be any
time constraints between client and server. How to remove this security
check?
sendittokeith@yahoo.com - 13 Jul 2006 21:32 GMT
I have the same need.  Have you ever found a solution for this?

> Documentation about <timeToleranceInSeconds> Element says:
>
[quoted text clipped - 14 lines]
> time constraints between client and server. How to remove this security
> check?
Sergey Pikhulya - 13 Jul 2006 21:41 GMT
Unfortunately no :(

If you will manage to do it please post in this thread. I will do same.

> I have the same need.  Have you ever found a solution for this?
>
[quoted text clipped - 16 lines]
> > time constraints between client and server. How to remove this security
> > check?
Spilafis - 06 Sep 2006 20:56 GMT
> Documentation about <timeToleranceInSeconds> Element says:
>
[quoted text clipped - 14 lines]
> time constraints between client and server. How to remove this security
> check?

I have a problem with this. My client application is not reading the timeToleranceInSeconds setting from the app.config file. Could you make this work at least inside the 24 hours limit?.
I'll post if I can find a solution.

Posted from http://www.topxml.com/renntp using reNNTP: the website based NNTP reader.
Paul B - 30 Nov 2006 20:32 GMT
> Documentation about <timeToleranceInSeconds> Element says:
>
[quoted text clipped - 14 lines]
> time constraints between client and server. How to remove this security
> check?

I have the same problem.  Would be ideal if they made this configurable for any time period not just 24hrs.

BizTalk Utilities - Frustration free BizTalk Adapters
http://www.topxml.com/biztalkutilities

Free Magazines

Get these publications absolutely FREE for up to 12 months. There are no hidden fees and no obligation. Simply choose a title, complete the application form and submit it. Read more ...

Oracle MagazineNetwork ComputingComputer WorldBio-IT WorldeWeekInformation WeekInfosecurity
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.