axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Jayasekara (Updated) (JIRA)" <>
Subject [jira] [Updated] (RAMPART-357) Timestamp verification handled at two locations in different ways
Date Tue, 14 Feb 2012 08:11:59 GMT


Amila Jayasekara updated RAMPART-357:

    Attachment: rampart_357_trunk.patch

Hi Hasini,

I slightly modified your patch so that it suits to current Rampart Trunk (after wss4j migration).
Please review this.

> Timestamp verification handled at two locations in different ways
> -----------------------------------------------------------------
>                 Key: RAMPART-357
>                 URL:
>             Project: Rampart
>          Issue Type: Bug
>            Reporter: Hasini Gunasinghe
>         Attachments: rampart_357.patch, rampart_357_trunk.patch
> Currently, when verifying timestamp, 'Expired' is verified in WSS4J level if timestampStrict
> 'Created' is verified in PolicyBasedResultsValidator.
> timestampMaxSkew is taken into consideration only when verifying 'Created' in timestamp
inside PolicyBasedResultsValidator.
> IMO, both 'Expired' and 'Created' should be verified in PolicyBasedResultsValidator in
a consistent way, taking timestampMaxSkew into consideration in both the occasions.
> Hence the proposed solution is like below:
> -Disable timestampStrict in WSConfig by default through Rampart. 
> -Verify both 'Expired' and 'Created' in PolicyBasedResultsValidator.
> -Allow to enable verification at WSS4J level through rampart config, if someone needs

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message