Network Deployment (Distributed operating systems), v8.0 > Reference > Sets


Encryption information configuration settings: Methods

Use this page to configure the encryption and decryption parameters for the signature method, digest method, and canonicalization method.

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 admin console page...

  1. Click Applications > Application Types > WebSphere enterprise applications > application_name and complete one of the following steps:

  2. Select None or Dedicated encryption information. The application server 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 described in this topic.

Fix packs that include updates to the SDK might overwrite unrestricted policy files. Back up unrestricted policy files before you apply a fix pack and reapply these files after the fix pack is applied.


Encryption information name

Name for the encryption information.


Key locator reference

Name used to reference the key locator.

We 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...

  1. Click Security > JAX-WS and JAX-RPC security runtime.

  2. Under Additional properties, click Key locators.

To configure the key locators on the server level...

  1. Click Servers > Server Types > WebSphere application servers > server_name

  2. Under Security, click JAX-WS and JAX-RPC security runtime.

    Mixed-version environment: In a mixed node cell with a server using Websphere Application Server version 6.1 or earlier, click Web services: Default bindings for Web Services Security.mixv

  3. Under Additional properties, click Key locators.

To configure the key locators on the application level...

  1. Click Applications > Application Types > WebSphere enterprise applications > application_name.

  2. Under Modules, click Manage modules > URI_name.

  3. Under Web Services Security Properties, you 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

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

The following algorithms are supported:

If an InvalidKeyException error occurs and you are using the 129xxx or 256xxx encryption algorithm, the unrestricted policy files might not exist in the configuration.


Java Cryptography Extension

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...

WAS_HOME/java/jre/lib/security/
) prior to overwriting them in case to restore the original files later.

Your country of origin might have restrictions on the import, possession, use, or re-export to another country, of encryption software. Before downloading or using the unrestricted policy files, check the laws of your country, its regulations, and its policies concerning the import, possession, use, and re-export of encryption software, to determine if it is permitted.


Application server platforms and IBM Developer Kit, Java Technology Edition v1.4.2

To download the policy files, complete one of the following sets of steps:

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


Data encryption algorithm

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. See the Key encryption algorithm field description.
Basic Security Profile compliance tips
Configure encryption using JAX-RPC to protect message confidentiality at the application level


Related


Encryption information collection
Key locator collection

+

Search Tips   |   Advanced Search