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 Future consideration
Created by Guest
Created on Nov 27, 2024

add a TN3270 configuration option to disable the check for Server name & Certificate name to match

Configurable  Option to disable Verify Certificate

We have encountered a situation with our TKEs at RBC.

We had LPAR site certificates included in the TN3270 ring before and removed thus only TN3270 user certificate is in the keyring.

More specifically, if a user connected TN3270 on TICF, TICF site certificate(ticf.fg.rbc.com) was sent to the clients and if tnocc was targeted then tnocc.fg.rbc.com certificate was sent.

Now no matter what a user targets tnocc or a lpar, only tnocc.rbc.com certificate is sent.

 

Recently we changed our Certificate names to drop the .fg , as part of some security requirement, so we no longer reveal our dns. We used to be tnocc.fg.rbc.com, but now are tnocc.rbc.com

As a result, our Hostname (Server Name: tnocc.fg.rbc.com) does not match the CN (Certificate Name: tnocc.rbc.com) for our TN320 certificate

This causes an authentication error (Certificate Name mismatch) when we try using the TN3270 certificate to configure our TKE 3270 session

We would like a TKE menu where we can edit the SSL properties similar to what PCOMM has to disable the check for Server name & Certificate name to match

Idea priority Medium