Minh wrote:I have.
For some reason, my clock didn't "spring forward" today, so I set it manually.
When I tried to make a call to a Web Service that's protected by UserNameToken's which we're using Microsoft.Web.Services2 to access, and getting this error:
Type = SecurityFault
Message = Message Expired
Type = Exception
Message = At least one timestamp has expired.
And when I set my clock back an hour, everything works just fine. Weird?
(whoops shoulda posted to TechOff)
This is because WSE checks to ensure that the times on the server and the client agree on the time--this helps to prevent replay attacks.
I'm guessing your server hasn't been updated?