[ https://issues.apache.org/jira/browse/RAMPART-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13210089#comment-13210089 ]
Hudson commented on RAMPART-357: -------------------------------- Integrated in Rampart #758 (See [https://builds.apache.org/job/Rampart/758/]) Fixing issue RAMPART-357. Applying the patch provided (Revision 1243894) Result = SUCCESS amilaj : Files : * /axis/axis2/java/rampart/trunk/modules/rampart-core/src/main/java/org/apache/rampart/PolicyBasedResultsValidator.java * /axis/axis2/java/rampart/trunk/modules/rampart-core/src/main/java/org/apache/rampart/RampartMessageData.java * /axis/axis2/java/rampart/trunk/modules/rampart-core/src/main/java/org/apache/rampart/policy/builders/RampartConfigBuilder.java * /axis/axis2/java/rampart/trunk/modules/rampart-core/src/main/java/org/apache/rampart/policy/model/RampartConfig.java > Timestamp verification handled at two locations in different ways > ----------------------------------------------------------------- > > Key: RAMPART-357 > URL: https://issues.apache.org/jira/browse/RAMPART-357 > Project: Rampart > Issue Type: Bug > Reporter: Hasini Gunasinghe > Attachments: rampart_357.patch, rampart_357_trunk.patch, > rampart_patch_trunk_v2.patch > > > Currently, when verifying timestamp, 'Expired' is verified in WSS4J level if > timestampStrict enabled. > '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 it. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: java-dev-unsubscr...@axis.apache.org For additional commands, e-mail: java-dev-h...@axis.apache.org