Encryption information configuration settings

Use this page to configure the encryption and decryption parameters.

The specifications that are listed on this page for the signature method, digest method, and canonicalization method are located in the World Wide Web Consortium (W3C) document entitled, XML Encryption Syntax and Processing: W3C Recommendation 10 Dec 2002.

To view this administrative console page, complete the following steps:

  1. Click Applications > Enterprise Applications > appname and complete one of the following steps:

    • Under Related Items, click EJB modules or Web modules > URI_file_name > Web Services: Client Security Bindings. Under Request sender binding, click Edit. Under Additional properties, click Encryption Information.

    • Under Related Items, click EJB modules or Web modules > URI_file_name > Web Services: Server Security Bindings. Under Response sender binding, click Edit. Under Additional properties, click Encryption Information.

  2. Select None or Dedicated encryption information. WAS can have either one or no encryption configurations for the request sender and the response sender bindings. If you are not using encryption, select None. To configure encryption for either of these two bindings, select Dedicated encryption information and specify the configuration settings using the fields that are described in this article.

Encryption information name

Name of the key locator configuration that retrieves the key for XML digital signature and XML encryption.

Key locator reference

Name that is used to reference the key locator.

One can configure these key locator reference options on the cell level, the server level, and the application level. The configurations that are listed in the field are a combination of the configurations on these three levels.

To configure the key locators on the cell level, complete the following steps:

  1. Click Security > Web services.

  2. Under Additional properties, click Key locators.

To configure the key locators on the server level, complete the following steps:

  1. Click Servers > Application servers > servername.

  2. Under Security, click Web services: Default bindings for Web services security.

  3. Under Additional properties, click Key locators.

To configure the key locators on the application level, complete the following steps:

  1. Click Applications > Enterprise applications > appname.

  2. Under Related items, click EJB modules > URI_name.

  3. Under Additional properties, one can access the key locators for the following bindings:

    • For the Request sender, click Web services: Client security bindings. Under Request sender binding, click Edit. Under Additional properties, click Key locators.

    • For the Request receiver, click Web services: Server security bindings. Under Request receiver binding, click Edit. Under Additional properties, click Key locators.

    • For the Response sender, click Web services: Server security bindings. Under Response sender binding, click Edit. Under Additional properties, click Key locators.

    • For the Response receiver, click Web services: Client security bindings. Under Response receiver binding, click Edit. Under Additional properties, click Key locators.

Encryption key name

Name of the encryption key that is resolved to the actual key by the specified key locator.

Data type String

Key encryption algorithm

Specifies the algorithm uniform resource identifier (URI) of the key encryption method.

The following algorithms are supported:

By default, the Java Cryptography Extension (JCE) is shipped with restricted or limited strength ciphers. To use 192-bit and 256- bit Advanced Encryption Standard (AES) encryption algorithms, apply unlimited jurisdiction policy files. Before downloading these policy files, back up the existing policy files (local_policy.jar and US_export_policy.jar in the WAS_HOME/jre/lib/security/ directory) prior to overwriting them in case you want to restore the original files later. To download the policy files, complete either of the following sets of steps:

  • For WAS platforms using IBM Developer Kit, Java Technology Edition V1.4.2, including the AIX, Linux, and Windows platforms, one can obtain unlimited jurisdiction policy files by completing the following steps:

    1. Go to the following Web site: http://www.ibm.com/developerworks/java/jdk/security/index.html

    2. Click Java 1.4.2

    3. Click IBM SDK Policy files.

      The Unrestricted JCE Policy files for SDK 1.4 Web site is displayed.

    4. Enter your user ID and password or register with IBM to download the policy files. The policy files are downloaded onto your machine.

  • For WAS platforms using the Sun-based Java Development Kit (JDK) V1.4.2, including the Solaris environments and the HP-UX platform, one can obtain unlimited jurisdiction policy files by completing the following steps:

    1. Go to the following Web site: http://java.sun.com/j2se/1.4.2/download.html

    2. Click Archive area.

    3. Locate the Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction Policy Files 1.4.2 information and click Download. The jce_policy-1_4_1.zip file is downloaded onto your machine.

After following either of these sets of steps, two JAR files are placed in the Java virtual machine (JVM) jre/lib/security/ directory.

Data encryption algorithm

Specifies the algorithm Uniform Resource Identifiers (URI) of the data encryption method.

The following algorithms are supported:

By default, the JCE ships with restricted or limited strength ciphers. To use 192-bit and 256- bit AES encryption algorithms, apply unlimited jurisdiction policy files. For more information, see the Key encryption algorithm field description.