The security handler on the request sender side of the SOAP message enforces the security constraints, located in...ibm-webservicesclient-ext.xmi
...and bindings, located...ibm-webservicesclient-bnd.xmi
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.
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...
You can select multiple parts of a message to sign digitally. The following list contains the integrity options:
- Time stamp
- Security token
You can select multiple parts of a message to encrypt. The following list contains the confidentiality options:
- Body content
- Username token
Security token You can insert only one token into the message. The following list contains the security token options:
- Basic authentication, which requires both a user name and a password
- Identity assertion, which requires a user name only
- X.509 binary security token
- LTPA binary security token
- Custom token , which is pluggable and supports custom-defined tokens in the SOAP message
Timestamp You can have a time stamp to indicate the timeliness of the message.
See AlsoResponse sender
Securing Web services using XML encryption