[SWS-538] Add support for XWSS 3.1 Created: 08/Jul/09  Updated: 04/May/12  Resolved: 19/May/10

Status: Closed
Project: Spring Web Services
Component/s: Security
Affects Version/s: None
Fix Version/s: 2.0 M2

Type: Improvement Priority: Minor
Reporter: Support Tech Assignee: Tareq Abedrabbo
Resolution: Complete Votes: 4
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified


 Description   

Created on behalf of customer:

Can the current distribution be upgraded to use the latest XWSS 3.1 distribution? There are issues with DST timezone handing that the newer versions resolve.



 Comments   
Comment by Rajesh Kamisetty [ 16/Jul/09 ]

XWSS has started adding one hour from 9 PM EST instead of 2 AM EST - applying dst logic 5 hours ahead of time. This resulted in WS-Security Headers carrying incorrect timestamp.

The relavent bug in XWSS 2.x and 3.0 is documented here :
https://xwss.dev.java.net/issues/show_bug.cgi?id=28

Thank you for taking this up.

Comment by Arjen Poutsma [ 26/Jul/09 ]

Upgrading from XWSS 2 to 3 is not a simple upgrade, as I believe the API is not 100% backwards compatible. Therefore, we need to wait with this for the next major release.

In the mean time, using the WSS4J security configuration gives a good workaround.

Comment by Tareq Abedrabbo [ 09/Mar/10 ]

I'm only able to locate version 3.0 on sun's maven repo. Anyone knows whether version 3.1 is published to any public repo?

Comment by Arjen Poutsma [ 09/Mar/10 ]

I can only see 3.0 in the repo's as well. Let's start with that, and hope that we find 3.1 later (and that is compatible).

Comment by Tareq Abedrabbo [ 02/Apr/10 ]

I updated the XWSS dependency to 3.0 since 3.1 is not available on a public repo yet. For the moment only the old configuration method is available since the new one, based on WS-Policy, seems to have strong dependencies on Metro. If anyone is willing to help with that, I'll be glad to assist.

Comment by Arjen Poutsma [ 04/May/12 ]

Closing old issues

Generated at Mon Dec 11 04:09:08 UTC 2017 using JIRA 6.4.14#64029-sha1:ae256fe0fbb912241490ff1cecfb323ea0905ca5.