Java Web services, Granular use of WS-Security

Applying WS-Security at the operation or message level

From the developerWorks archives

Dennis Sosnoski

Date archived: December 19, 2016 | First published: August 04, 2009

WS-Security for SOAP Web services doesn't have to be an all-or-nothing proposition. By configuring WS-Security at the operation or message level, you can apply an appropriate degree of protection to every exchange, reducing or eliminating the WS-Security overhead for operations that don't need full protection. Dennis Sosnoski continues his Java Web services series with a look at granular WS-Security in Web Services Description Language (WSDL) using Apache Axis2 and Rampart.

This content is no longer being updated or maintained. The full article is provided "as is" in a PDF file. Given the rapid evolution of technology, some steps and illustrations may have changed.



static.content.url=http://www.ibm.com/developerworks/js/artrating/
SITE_ID=1
Zone=Java development, SOA and web services, Open source
ArticleID=418048
ArticleTitle=Java Web services: Granular use of WS-Security
publish-date=08042009