Skip to Main Content
IBM Data and AI Ideas Portal for Customers


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:

Post your ideas

Post ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The product management team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

Additional Information

To view our roadmaps: http://ibm.biz/Data-and-AI-Roadmaps

Reminder: This is not the place to submit defects or support needs, please use normal support channel for these cases

IBM Employees:

The correct URL for entering your ideas is: https://hybridcloudunit-internal.ideas.aha.io


Status Under review
Created by Guest
Created on Jun 17, 2022

Make encrypted connection to access server with chcclp without reading tls.properties

We have an environment where encrypted communication is mandatory.

When users want to execute chcclp scripts on the access server, they need to read the tls.properties file of the access server to find the location of the trust store.

But in the tls.properties, the passwords of the key and trust store are visible. So if we give read access to tls.properties, they immediatly have the passwords of the trust and key store.

Can this be solved by:

- adding a parameter to chcclp with the path of the trust store?

- put the passwords of the key and trust store encrypted in tls.properties?

- do not put the passwords of the key and trust store in tls.properties?

- check for a variable that is set with the location to the trust store?

- ... ?

Needed By Week