Timestamp validation fails! Why?

This explains the common issues in wsse:Timestamp validation and the possible fixes.

Date: Mon, 30th Jul, 2007
Level: Intermediate
Reads: 5269 Comments: 0 | Login or register to post comments
Ruchith Fernando
Software Engineer
WSO2 Inc.

We usually develop and test secure Web services applications in one machine. Then, when we actually test this application with a remote client, some of the initial issues we run into are timestamp validation issues. This is mainly due to the clocks of the two machines not being in sync. In real life scenarios, we certainly cannot expect clocks to be in sync. You can synchronize clocks across machines automatically with tools that use Network Time Protocol.

Apache Rampart/Java introduces a new configuration assertion to allow time differences between communicating hosts.

<timestampMaxSkew>value<timestampMaxSkew>

The "value" must be the allowed time skew in seconds and must be specified as an integer. By default Apache Rampart/Java tolarates a maximum time skew of five (5) minutes (300 seconds).

The <timestampMaxSkew> assertion must be placed within the <RampartConfig> assertion as an immediate child element.

 

Applies To

1. Apache Rampart/Java

 

 

library project main code
Learn Cloud
Learn
Cloud

The WSO2 Application Server is a reliable application server that can host your enterprise web applications. The WSO2 Application Server as a Service is offered in StratosLive, the WSO2 Platform as a Service. This article explains how a simple web application can be developed and deployed from Carbon Studio to the WSO2 Application Server...

Latest Webinar
Different groups within an organization need to monitor different Key Performance Indicators (KPIs) - An operations team will be interested in the response times of business services and loads of each service,..
Thursday, February 9th 2012, 09.00 AM (PST)

Thursday, February 9th 2012, 10.00 AM (GMT)