Request receiver

The security handler on the request receiver side of the Simple Object Access Protocol (SOAP) message enforces the security specifications defined in the IBM extension deployment descriptor (ibm-webservices-ext.xmi) and bindings (ibm-webservices-bnd.xmi). The request receiver defines the security requirement of the SOAP message. The security constraint for request sender must match the security requirement of the request receiver for the server to accept the request. If the incoming SOAP message does not meet all the security requirements defined, then the request is rejected with the appropriate fault code returned to the sender. For security tokens, the token is validated using Java Authentication and Authorization Service (JAAS) login configuration and authenticated identity is set as the identity for the downstream invocation.

For example, if there is a security requirement to have the SOAP body digitally signed by Joe Smith and if the SOAP body of the incoming SOAP message is not signed by Joe Smith, then the request is rejected.

You can define the following security requirements for the request receiver...

Required integrity (digital signature) You can select multiple parts of a message to sign digitally. The following list contains the integrity options:

  • Body

  • Time stamp

  • Security token

Required confidentiality (encryption) You can select multiple parts of a message to encrypt. The following list contains the confidentiality options:

  • Body content

  • Token

You can have multiple security tokens. The following list contains the security token options:

Received time stamp You can have a time stamp for checking the timeliness of the message.

  • Time stamp


See Also

Response sender
Response receiver
Request sender
Securing Web services using XML encryption
Configuring the server for request decryption: choosing the decryption method