[A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [K] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W] [X] [Y] [Z] [0-9]

By:	Bruce Bahlmann Preethi Ramkumar

Specifies ways to encode authentication and other security tokens in Simple Object Access Protocol (SOAP) message headers. Web Services Security Language (WS-Security) outlines encoding mechanisms for user IDs/passwords, (X.509) certificates, Kerberos tickets, and (SAML) assertions.

WS-Security (Web Services Security) is a proposed IT industry standard that addresses security when data is exchanged as part of a Web service. WS-Security is one of a series of specifications from an industry group that includes IBM, Microsoft, and Verisign. Related specifications include the Business Process Execution Language (BPEL), WS-Coordination, and WS-Transaction.
WS-Security also specifies how to associate a security token with a message, without specifying what kind of token is to be used.The WS-Security specification is an activity of the Web Service Interoperability Organization (WS-I Organization) which is an industry-wide effort at standardizing how Web services are requested and delivered.

"...(Web Services Security) Standards framework for secure web services, based on SOAP. WS-Security defines additional headers that can be added to a SOAP message to implement integrity and confidentiality in web services applications. It provides a foundation for further security specifications that are under development, including WS-Policy, WS-Trust and WS-Federation. Originally put forward by IBM, Microsoft and Verisign, WS-Security became the responsibility of the OASIS e-business standards body in July 2002". [Procullux Media Ltd]

"...OASIS Standard specification describes enhancements to SOAP messaging to provide message integrity and confidentiality. The specified mechanisms can be used to accommodate a wide variety of security models and encryption technologies. This specification also provides a general-purpose mechanism for associating security tokens with message content. No specific type of security token is required, the specification is designed to be extensible (i.e.. support multiple security token formats). For example, a client might provide one format for proof of identity and provide another format for proof that they have a particular business certification".[OASIS]

oracle - Tutorial: Security for Web Services .
microsoft - Web Service Security Guide.
xtradyne - FAQ.

java.sun - XML and Web Services Security .
informit - Web Services Security.

vordel - Introducing Vordel SOAPbox 3.1
websense - Websense Web Security Suite.

Ultra-Slim Universal Flat Wall Mount For 32" to 56" Ultra-Thin Screens Only by Peerless (Too low to display)

Web Services Security by Mark O'Neill ($32.99)
Expert Web Services Security in the .NET Platform by Brian Nantz ($40.49)
Enterprise Web Services Security (Internet Series) by Rickland Hollar ($34.81)
Security for Web Services and Service-Oriented Architectures by Elisa Bertino ($56.20)
Mastering Web Services Security by Bret Hartman ($60.00)
Web Services Security and E-business by G. Radhamani ($64.08)
Web Service Security: Scenarios, Patterns, and Implementation Guidance for Web Services Enhancements (WSE) 3.0 (Patterns & Practices) by Microsoft Corporation ($31.49)
Mobility, Security and Web Services: Technologies and Service-oriented Architectures for a New Era of IT Solutions (German Edition) by Gerhard Wiehler ($60.00)

Can Birds-Eye.Net help you or your Company?
Receive your Birds-Eye.Net articles and white papers hot off the presses by adding our RSS feed to your reader.

 [A] [B] [C] [D] [E] [F] [G] [H] [I] [J] [K] [L] [M] [N] [O] [P] [Q] [R] [S] [T] [U] [V] [W] [X] [Y] [Z] [0-9]