Apache has released 1.0 of WSS4J (WS-Security) and 1.0 of Sandesha (WS-Reliability), both running on top of Axis.
WSS4J can be used to sign and verify SOAP Messages with WS-Security information, implementing the OASIS Web Service Security standard, the Username Token profile V1.0, and the X.509 Token Profile V1.0. It is also able to emulate older WSS specifications.
Sandesha provides a complete support for WS-ReliableMessaging specification allowing a reliable communication between web services as well as web services and clients.
What are your thoughts of these products? Are they useful to you?
-
Apache releases two Web Services Packages (8 messages)
- Posted by: Joseph Ottinger
- Posted on: August 01 2005 02:02 EDT
Threaded Messages (8)
- Security by Lei Jin on August 01 2005 03:54 EDT
- Security by Joseph Ottinger on August 01 2005 04:21 EDT
- Relationship between Security and reliability by Syed Naqvi on August 03 2005 06:21 EDT
- Relationship between Security and reliability by Syed Naqvi on August 03 2005 06:24 EDT
- Security - Two packages by justin whiting on August 03 2005 15:33 EDT
- Security by Joseph Ottinger on August 01 2005 04:21 EDT
- Any download link? by Maurizio Turatti on August 01 2005 11:30 EDT
- This is good news by Sunil D'Monte on August 01 2005 23:59 EDT
- It works (at least for me...) by Fran?ois Lemaire on August 02 2005 03:10 EDT
-
Security[ Go to top ]
- Posted by: Lei Jin
- Posted on: August 01 2005 03:54 EDT
- in response to Joseph Ottinger
Why is that "two Web Services security packages"? What does WS-ReliableMessaging have to do with security? -
Security[ Go to top ]
- Posted by: Joseph Ottinger
- Posted on: August 01 2005 04:21 EDT
- in response to Lei Jin
I.. uh.. have no answer for that. The title has been changed. Thank you. -
Relationship between Security and reliability[ Go to top ]
- Posted by: Syed Naqvi
- Posted on: August 03 2005 06:21 EDT
- in response to Joseph Ottinger
Relationship between WS Security and Reliable messaging
A secure web service should be always available to the Authorize user . Without reliable messaging the WS availability is at risk . We can call a WS as secure if it available to authorize user is atself at risk. Hence WS security and WS reliable messagining go together .
Syed -
Relationship between Security and reliability[ Go to top ]
- Posted by: Syed Naqvi
- Posted on: August 03 2005 06:24 EDT
- in response to Joseph Ottinger
Relationship between WS Security and Reliable messaging
A secure web service should be always available to the Authorize user . Without reliable messaging the WS availability is at risk . We can call a WS as secure only if it is available to authorize user , all the time . Hence WS security and WS reliable messagining go together .
Syed -
Security - Two packages[ Go to top ]
- Posted by: justin whiting
- Posted on: August 03 2005 15:33 EDT
- in response to Lei Jin
I thought security is not only encryption but validation of sending parties, and validation of sent data - hence the "reliable" seems apprpriate -
Any download link?[ Go to top ]
- Posted by: Maurizio Turatti
- Posted on: August 01 2005 11:30 EDT
- in response to Joseph Ottinger
From where it is possible to download the WSS4J distribution? Looks like it is still necessary to go through CVS... -
This is good news[ Go to top ]
- Posted by: Sunil D'Monte
- Posted on: August 01 2005 23:59 EDT
- in response to Joseph Ottinger
I had been shying away from WS-Security because it didn't have a 1.0 release yet. Am definitely going to try it out now. One question though - is it really interoperable with a .NET client? My service is on Axis, but the clients will be Visual Basic .NET. I'd hate to use WSS4J only to find that ".NET Web Services Enhancements (WSE) 2.0 SP2" doesn't work like it should. :)
Regards,
Sunil -
It works (at least for me...)[ Go to top ]
- Posted by: Fran?ois Lemaire
- Posted on: August 02 2005 03:10 EDT
- in response to Sunil D'Monte
Hello,
I've been using a version of WSS4J retrieved from CVS three months ago as client to a WSE 2.0 SP3 service, and it worked. The main problem I had is to synchronize the clients clock with the servers clock (since messages are timestamped), but this has nothing to do with the implementation :)
Regards,
François