98 lines
5.7 KiB
HTML
98 lines
5.7 KiB
HTML
|
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
|
||
|
|
<html>
|
||
|
|
<head>
|
||
|
|
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
|
||
|
|
<LINK rel="stylesheet" type="text/css" href="../../../rzahg/ic.css">
|
||
|
|
|
||
|
|
<title>Configure the Web services client for response decryption</title>
|
||
|
|
</head>
|
||
|
|
|
||
|
|
<BODY>
|
||
|
|
<!-- Java sync-link -->
|
||
|
|
<SCRIPT LANGUAGE="Javascript" SRC="../../../rzahg/synch.js" TYPE="text/javascript"></SCRIPT>
|
||
|
|
|
||
|
|
<h5><a name="wsseccfencclres"></a>Configure the Web services client for response decryption</h5>
|
||
|
|
|
||
|
|
<p>This task provides the steps needed to configure the client for response decryption. Use these steps to modify the extensions to indicate which parts of the response that you want to decrypt. Before configuring the client for response decryption, you must know what server parts encrypt the response. The server response encryption and client response decryption configurations must match. The steps in this task also describe how to configure the bindings to indicate how to decrypt the parts of the response.</p>
|
||
|
|
|
||
|
|
<p>Perform the following steps in the WebSphere Development Studio Client for iSeries to configure the parts of the SOAP response that you must decrypt:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li><p>Open the webservicesclient.xml file in the Web Services Client Editor of the WebSphere Development Studio Client for iSeries. For more information, see <a href="astk.htm">Configure your Web services application</a>.</p></li>
|
||
|
|
|
||
|
|
<li><p>Click the <strong>Security Extensions</strong> tab.</p></li>
|
||
|
|
|
||
|
|
<li><p>Expand the <strong>Response Receiver Configuration --> Required Confidentiality</strong> settings.</p></li>
|
||
|
|
|
||
|
|
<li><p>Select the parts of the message that you must decrypt by clicking <strong>Add</strong>
|
||
|
|
and selecting one of the following two message parts:</p>
|
||
|
|
<ul>
|
||
|
|
<li><p><strong>Bodycontent</strong>
|
||
|
|
<br>This is the user data portion of the message.</p></li>
|
||
|
|
|
||
|
|
<li><p><strong>Usernametoken</strong>
|
||
|
|
<br>This is the basic authentication information, if selected.</p></li>
|
||
|
|
</ul>
|
||
|
|
<p>The information selected in this step is encrypted by the server in the response sender.</p>
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> A username token is typically not sent in the response. Thus, you usually do not need to select <strong>Usernametoken</strong>.</p></li>
|
||
|
|
|
||
|
|
<li><p>Save the file.</p></li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<p>Next, perform the following steps in the Web Services Client Editor to configure the information needed to decrypt the required message parts:</p>
|
||
|
|
|
||
|
|
<ol>
|
||
|
|
<li><p>Click the <strong>Port Binding</strong> tab.</p></li>
|
||
|
|
|
||
|
|
<li><p>Expand the <strong>Security Response Receiver Binding Configuration --> Encryption Information</strong> settings. For more information on encrypting and decrypting SOAP messages, see <a href="wsseccfxmlenc.htm">XML encryption</a>.</p></li>
|
||
|
|
|
||
|
|
<li><p>Click <strong>Edit</strong> to view the encryption information. The following table describes the purpose for each of this information. Some of these definitions are based on the <a href="http://www.w3.org/TR/xmldsig-core" target="_">XML-Signature Syntax and Processing specification</a> <img src="www.gif" width="18" height="15" alt="Link outside Information Center"> (http://www.w3.org/TR/xmldsig-core).</p>
|
||
|
|
|
||
|
|
<table border="1" cellpadding="3" cellspacing="0">
|
||
|
|
<tr valign="top">
|
||
|
|
<th>Name</th>
|
||
|
|
<th>Purpose</th>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr valign="top">
|
||
|
|
<td><strong>Encryption name</strong></td>
|
||
|
|
<td>The encryption name refers to the alias used for the encryption information entry.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr valign="top">
|
||
|
|
<td><strong>Data encryption method algorithm</strong></td>
|
||
|
|
<td>The data encryption method algorithms are designed for encrypting and decrypting data in fixed size, multiple octet blocks.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr valign="top">
|
||
|
|
<td><strong>Key encryption method algorithm</strong></td>
|
||
|
|
<td>The key encryption method algorithms are public key encryption algorithms specified for encrypting and decrypting keys.</td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr valign="top">
|
||
|
|
<td><strong>Encryption key name</strong></td>
|
||
|
|
<td>The encryption key name represents a Subject from a certificate found by the encryption key locator. The Subject is used by the key encryption method algorithm to decrypt the secret key. The secret key is used to decrypt the data.
|
||
|
|
<p><strong>Note:</strong> The key chosen must be a private key of the client. Encryption must be done using the public key and decryption must be done by the private key (personal certificate).</p>
|
||
|
|
|
||
|
|
<p>For example, the personal certificate of the client is CN=Alice, O=IBM, C=US. Therefore, the client contains the public and private key pair. The target server that sends the response encrypts the
|
||
|
|
secret key using the public key for CN=Alice, O=IBM, C=US. The client decrypts the secret key using the private key for CN=Alice, O=IBM, C=US.</p></td>
|
||
|
|
</tr>
|
||
|
|
|
||
|
|
<tr valign="top">
|
||
|
|
<td><strong>Encryption key locator</strong></td>
|
||
|
|
<td>The encryption key locator represents a reference to a key locator implementation. For more information on configuring key locators, see <a href="wsseccfkeyloc.htm">Configure key locators</a>.</td>
|
||
|
|
</tr>
|
||
|
|
</table><p></p></li>
|
||
|
|
|
||
|
|
<li><p>Save the file.</p></li>
|
||
|
|
</ol>
|
||
|
|
|
||
|
|
<p><strong>Note:</strong> For decryption, the encryption key name that is chosen must refer to a personal certificate that can be located by the client key locator. The Subject (owner field of the certificate)
|
||
|
|
of the personal certificate should be entered in the Encryption key name, this is typically a Distinguished Name (DN). The default key locator uses the Encryption key name to find the key within the keystore. If you write a custom key locator, the encryption key name can be anything used by the key
|
||
|
|
locator to find the correct encryption key. The encryption key locator references the implementation class that locates the correct key store where this alias and certificate exists.</p>
|
||
|
|
|
||
|
|
</body>
|
||
|
|
</html>
|
||
|
|
|