Web Service Attributes Editor: Input Message

See Also 

In the Quality of Service tab's Operation section, on the service side, you can add Quality of Service security to a specific web service operation. Security mechanism at this level is used to specify what is being protected and the level of protection required.

In this section, you can specify parts of a message that require integrity protection (digital signature) and/or confidentiality (encryption). When you do this, the specified part of the message, outside of security headers, requires signature and/ or encryption. For example, a message producer might submit an order that contains an orderID header. The producer signs and/or encrypts the orderID header (the SOAP message header) and the body of the request (the SOAP message body). Parts that can be signed and/or encrypted include the body, the header, the local name of the SOAP header, and the namespace of the SOAP header.

You can also specify arbitrary elements in the message that require integrity protection and/or confidentiality. Because of the mutability of some SOAP headers, a message producer may decide not to sign and/or encrypt the SOAP message header or body as a whole, but instead sign and/or encrypt elements within the header and body. Elements that can be signed and/or encrypted include an XPath expression or a URI which indicates the version of XPath to use.

In the Input Message section of the WSIT configuration editor, you can select the following options for securing an input message:

Click Message Parts to specify which parts of the message need to be encrypted, signed, and/or required.

See Also
About Quality of Service

Legal Notices