You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Amila Jayasekara (Resolved) (JIRA)" <ji...@apache.org> on 2012/02/15 10:28:06 UTC
[jira] [Resolved] (RAMPART-357) Timestamp verification handled at
two locations in different ways
[ https://issues.apache.org/jira/browse/RAMPART-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Amila Jayasekara resolved RAMPART-357.
--------------------------------------
Resolution: Fixed
Patch is applied to trunk in revision 1243894. Therefore resolving this issue.
Thanks Hasini for the contribution.
Note: When applying this to 1.6 branch we can directly use rampart_357.patch file.
Thanks
AmilaJ
> 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-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org