Last post Nov 11, 2014 10:05 PM by Shawn - MSFT
Nov 10, 2014 05:05 AM|shabbir_215|LINK
I have WCF services which was access by the Client but they are having a issue with Clock Skew so we tried to increase our server time 2 minutes faster and it worked, Is there any solution that in future we don't have modify the clock time, Below is the
"System.ServiceModel.Security.MessageSecurityException, System.ServiceModel, Version=126.96.36.199, Culture=neutral, PublicKeyToken=b77a5c561934e089"
"The security timestamp is invalid because its creation time ('2014-11-03T09:22:20.432Z') is in the future. Current time is '2014-11-03T09:17:17.052Z' and allowed clock skew is '00:05:00'."
Thanks in Advance
Nov 10, 2014 05:55 AM|mike4u|LINK
Nov 10, 2014 09:21 AM|shabbir_215|LINK
Thanks for your reply, I tried to update the web.config on server side using settings mention in above link but didn't work.
Nov 11, 2014 12:36 AM|Shawn - MSFT|LINK
For this situation, you could try to create a custom binding to change the values of maximum skew time:
<localClientSettings maxClockSkew="00:07:00" />
<localServiceSettings maxClockSkew="00:07:00" />
For more information, see
How To: Set a Max Clock Skew on MSDN
Nov 11, 2014 04:08 AM|shabbir_215|LINK
Thanks for the code, should i add in server side or client side web.config ?
Nov 11, 2014 10:05 PM|Shawn - MSFT|LINK
You could try to add the custom binding both on the client side and server side configuration file.
Beisdes, you could also refer to the following links for more information: