Web Service Protocols

WS-Security

Virtuoso SOAP endpoints can be configured to require signed or encrypted access and to sign and/or encrypt any replies. Virtuoso's SOAP client can likewise encrypt and decrypt and sign and validate signatures. Symmetric and asymetric encryption algorithms are supported, including RSA, DSA, AES and Triple-DES. The digital signatures supported are: RSA-SHA1, DSA-SHA1, HMAC-SHA1.

The level of protocol support is based on following profiles of "OASIS Web Services Security (WSS) TC" specification:

WS-Security Core Specification 1.1 Username Token Profile 1.1 X.509 Token Profile 1.1 Also the Virtuoso WS-Security implementation have been tested for compatibility with Microsoft WSE 2.0 toolkit.

WS-Trust

The WS-Trust protocol complements WS-Security by adding a third-party issuer of trust tokens to the WS Security exchange. The Virtuoso implementation provides an API for building client, server and trust server functions.

The level of protocol support is based on "WS-Trust (Dec 2002)" specifcation.

WS-Reliable Messaging

Virtuoso has client- and server-side API for WS-Reliable Messaging (WSRM). The database has a system table for incoming and outgoing WSRM traffic; the developer can supply callback functions for processing different messages. The protocol implementation covers guaranteed delivery, guaranteed order and exactly once delivery. There is an object API for keeping track of conversations and message sequence.

The level of protocol support is based on "WS-ReliableMessaging?? (March 2004)" specification.

Getting Started

The source distribution's demo database has on-line tutorials for all these protocols and more. To get going, point the browser to http://localhost:8890/tutorial and choose Web Services.

There are additionally numerous examples in binsrc/tests/suite/ in the source tree. Look at thttp.sh to find the scripts that make up the WS Interop suite. This contains client- and server-side examples of all supported WS protocols, from basic SOAP onwards.