Skip to Main Content
IBM Z Software


This portal is to open public enhancement requests against IBM Z Software products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Future consideration
Created by Guest
Created on Jul 7, 2016

Enhance JVM Keystore resiliency if bad certificate encountered

Today, a JVM that utilizes SSL will earmark a keystore/keyring as invalid if any certificate within the keystore/keyring is missing a private key, regardless of it other certificates are valid and the problematic certificate is not even used within the Java environment. For JVMs within CICS, this exposes a Java deficiency that CICS native overcomes. When CICS encounters a bad certificate, it complains, but then continues to let other certificate within the keystore/keyring be utilized. Thus, a single bad certificate could make the entire keystore/keyring invalid for Java while CICS could simply fail on that one certificate. The JVM should be enhanced to be more resilient like CICS native is.

Idea priority High
  • Guest
    Reply
    |
    Aug 29, 2016

    .Keystore.load is implemented to conform to behavior documented by Oracle at http://docs.oracle.com/javase/8/docs/api/index.html?java/security/KeyStore.html . Customers expect this behavior to be consistent from release to release, so it will not be modified. However, a new class could be considered implementing the behavior as outlined in the RFE requirement, to continue processing after encountering a bad certificate and tracking those certificates as part of the KeyStore implementation. This requirement will therefore be treated as a candidate for future consideration.

  • Guest
    Reply
    |
    Jul 8, 2016

    Creating a new RFE based on Community RFE #91118 in product JAVA.