Skip to Main Content
IBM Z Hardware and Operating Systems Ideas Portal


This is the public portal for all IBM Z Hardware and Operating System related offerings. 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 Not under consideration
Workspace z/OS
Categories RACF
Created by Guest
Created on Nov 17, 2023

Define the conflicting certificates have same public key within RACF database

RACF database should have certificates with same public key to be defined. As long as certificates have different serial number, they should be consider as different certificates. 

Since Digicert has created two intermediate CA which have different serial number but same public key, it is necessary to have this function available. Considering Digicert is a world wide used certificate authority, more users may get impact in the future.  Clients may fail the SSL connection when it is pinning a specific Intermediate certificate, which is a practice we have seen many times.

Idea priority Medium
  • Guest
    Reply
    |
    Jan 2, 2024
    The problem was caused by the client side which pinned an intermediate CA certificate that has been renewed. This is a common problem with certificate pinning. The industry is moving away from certificate pinning.

    The server side can avoid the problem by just putting the server certificate in the key ring or the client side can remove the old intermediate CA certificate from the client key ring. If neither way is possible at the moment, a bypass can be done. Both the new and old intermediate CA certificates can be installed in RACF, but only one can be installed under CERTAUTH, while the other one is added under a different ID. Depends on the target client, the server key ring can pick which intermediate CA to be connected to, with the connect usage specified. Don?t put both in the same keyring though since the one get picked may not be the desired one for the target client. This is considered a temporary set up, the old intermediate CA should be removed from the server and client side eventually.