I am having an issue in which the service I am trying to consume runs on a server that the clock runs faster then mine. I have requested several times that they implement a more efficient process for keeping their time updated but it does not appear to be resolved.
Troubleshooting this issue I have noticed that there have been changes since the 2.1.0 release that allows for this type of issue by setting the rampart configuration ClockSkewBuffer.
It appears I may not be implementing this correctly because my clock skew buffer value equals 0 at the time of validating the response time stamp. This is happening during the token request and response. I continually receive the errors:
[rampart]Timestamp not valid: Created time is not valid
[rampart]Timestamp is not valid
Can someone please look at my policy file and tell me how I implement and ClockSkewBuffer of 3 seconds during the Token Service request?