Request sender

The security handler on the request sender side of the SOAP message enforces the security constraints, located in the ibm-webservicesclient-ext.xmi file, and bindings, located in the ibm-webservicesclient-bnd.xmi file. These constraints and bindings apply both to J2EE application clients or when Web services is acting as a client. The security handler acts on the security constraints before sending the SOAP message. For example, the security handler might digitally sign the message, encrypt the message, create a time stamp, or insert a security token.

The security handler on the request sender side of the Simple Object Access Protocol (SOAP) message enforces the security constraints, located in the ibm-webservicesclient-ext.xmi file, and the bindings, located in the ibm-webservicesclient-bnd.xmi file. These constraints and bindings apply both to J2EE application clients or when Web services is acting as a client. The security handler acts on the security constraints before sending the SOAP message. Request sender security constraints must match the security constraint requirements defined in the request receiver. For example, the security handler might digitally sign the message, encrypt the message, create a time stamp, or insert a security token. You can specify the following security requirements for the request sender and apply them to the SOAP message:

Integrity (digital signature)
You can select multiple parts of a message to sign digitally. The following list contains the integrity options:
Confidentiality (encryption)
You can select multiple parts of a message to encrypt. The following list contains the confidentiality options:
Security token
You can insert only one token into the message. The following list contains the security token options:
Timestamp
You can have a time stamp to indicate the timeliness of the message.