The <dfhwsse_configuration> element
Specifies configuration information for the security handler DFHWSSE1, which provides support for securing web services.
Used in:
- Service provider
- Service requester
Contained by:
Attributes:
| Name | Description |
|---|---|
| version | An integer denoting the version of the configuration information. The only valid value is 1. |
Contains:
- Either of the following elements:
- An optional <authentication> element.
- In a service requester pipeline, the <authentication> element specifies the type of authentication that must be used in the security header of outbound SOAP messages.
- In a service provider pipeline, the element specifies whether CICS uses the security tokens in an inbound SOAP message to determine the user ID under which work is processed.
- An optional <sts_authentication> element.
The action attribute on this element specifies what type of request to send to the Security Token Service. If the request is to issue an identity token, then CICS uses the values in the nested elements to request an identity token of the specified type.
- An optional <authentication> element.
- If you specify an <sts_authentication> element, you
must also specify an <sts_endpoint> element.
When this element is present, CICS uses the URI in the <endpoint> element to send a request to the Security Token Service.
- An optional, empty <expect_signed_body/> element.
The <expect_signed_body/> element indicates that the <body> of the inbound message must be signed. If the body of an inbound message is not correctly signed, CICS rejects the message with a security fault.
- An optional, empty <expect_encrypted_body/> element.
The <expect_encrypted_body/> element indicates that the <body> of the inbound message must be encrypted. If the body of an inbound message is not correctly encrypted, CICS rejects the message with a security fault.
- An optional <sign_body> element.
If this element is present, CICS will sign the <body> of the outbound message, using the algorithm specified in the <algorithm> element contained in the <sign_body> element.
- An optional <encrypt_body> element.
If this element is present, CICS will encrypt the <body> of the outbound message, using the algorithm specified in the <algorithm> element contained in the <encrypt_body> element.
- In provider pipelines only, an optional <reject_signature/> element.
If this element is present, CICS rejects any message that includes a certificate in its header that signs part or all of the message body. A SOAP fault is issued to the web service requester.
- In provider pipelines only, an optional <reject_encryption/> element.
If this element is present, CICS rejects any message that is partially or fully encrypted. A SOAP fault is issued to the web service requester.
Example
<dfhwsse_configuration version="1">
<sts_authentication action="issue">
<auth_token_type>
<namespace>http://example.org.tokens</namespace>
<element>UsernameToken</element>
</auth_token_type>
<suppress/>
</sts_authentication>
<sts_endpoint>
<endpoint>https://example.com/SecurityTokenService</endpoint>
</sts_endpoint>
<expect_signed_body/>
<expect_encrypted_body/>
<sign_body>
<algorithm>http://www.w3.org/2000/09/xmldsig#rsa-sha1</algorithm>
<certificate_label>SIGCERT01</certificate_label>
</sign_body>
<encrypt_body>
<algorithm>http://www.w3.org/2001/04/xmlenc#tripledes-cbc</algorithm>
<certificate_label>ENCCERT02</certificate_label>
</encrypt_body>
</dfhwsse_configuration>