This topic applies only on the z/OS operating system.

Using the z/OS hardware cryptography leveraging ICSF and RACF keystores

Integrated Cryptographic Service Facility (ICSF) is the software on a z/OS system that serves as an interface with the hardware where keys can be stored. IBMJCE4758RACFKS keystores handle certificates and keys managed in Resource Access Control Facility (RACF). The certificates are stored in RACF, but you can store keys in ICSF to achieve hardware crypto exploitation, such as encryption, decryption and signing

Before you begin

Note: The JCE4758RACFKS keystore type, is only available on the z/OS platform.

About this task

Note: If the key is going to be stored in the hardware, generating new keys in RACF requires using the ICSF option.

Procedure

  1. Make a backup copy of the original restricted local_policy.jar and US_export_policy.jar files.
  2. Obtain the Java unrestricted policy jars from the IBM developer kit: Security information Web site and place them on the WebSphere Application Server for z/OS system.
    Important: 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, you must 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.

    Complete the following steps:

    1. Click J2SE 1.4.2.
    2. Scroll down the page then click IBM SDK Policy files.
    3. Click Sign in and provide your IBM.com ID and password.
    4. Select Unrestricted JCE Policy files for SDK for all newer versions: Version 1.4.1 + and click Continue.
    5. View the license, select I agree, and click I confirm to continue.
    6. Click Download now.
    7. Download the unrestricted local_policy.jar and US_export_policy.jar files to your WebSphere Application Server for z/OS system and place them in the WAS_HOME/AppServer/java/lib/security directory.
    8. Use the chmod 644 command to change the file permissions so that the control and servant region address spaces can access the Java archive (JAR) files. For example:

      chmod 644 local_policy.jar
      chmod 644 US_export_policy.jar

  3. Start the required ICSF services. Refer to JAVA and ICSF documentation for more information.
  4. In the java.security file that is located under $JAVA_HOME/lib/security, Add the following IBMJCE4758 provider to the top of the provider list:
    security.provider.1=com.ibm.crypto.hdwrCCA.provider.IBMJCE4758
  5. Renumber the remaining providers in the provider list.
  6. Navigate to Security > Global Security > SSL.
  7. Select the JSSE repertoire that needs to reference the keyring with one or more ICSF certificates.
  8. Change the Key File Format and Trust File Format to JCE4758RACFKS. The URI must contain safkeyringhw instead of safkeyring, for example, safkeyringhw:///WASKeyring.
  9. Click OK, then click Save to apply these changes to the master configuration.

Results

A keystore is now available to configure SSL connections.

What to do next

You can continue securing communication between the client and server using this keystore file when setting up an SSL configuration.



In this information ...


IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic    

Terms of Use | Feedback

Last updated: Aug 29, 2010 10:43:27 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=v602web&product=was-nd-mp&topic=tsec_storecertkeysICSF
File name: tsec_storecertkeysicsf.html