Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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 Submitted
Workspace App Connect
Created by Guest
Created on Jan 16, 2025

ACE configuration object type Generic for CP4I needs to support base64 encoding for handling simple Openshift secrets instead of zip format

We are running the latest ACE SC-2 release on CP4I v16.1.0 on Openshift 4.14 on Azure Cloud.

We have a few integrations that connect to SFTP using an ssh-identity file/ssh key file. We have placed the private part of the ssh key file in Azure Key Vault Secret that is synced to Openshift secret using akv2k8s utility. The public part of ssh key is shared with the department who owns the SFTP server.

Today in order to get the Openshift secret (which contains the ssh private key) mounted on to ACE IntegrationServer pod, we use ACE configuration object type "generic" which requires that the contents of the secret be zipped. Just to get it zipped we had to use the Openshift pipelines which is an overkill, the main issue is the life-cycle management of it, where if the key is updated in Azure Key Vault, it gets synced to Openshift every 2 seconds, but then someone needs to be run the Openshift pipeline manually to refresh the secret referenced by the ACE configuraton object of type "Generic".

Therefore, we would expect that for simple ASCII secrets (Openshift secrets of type opaque), that you support a simple base64 encoding (like you do for object types serverconf and odbcini), rather than having to zip the secret contents. You could alternatively create a new ACE configuration type to handle the problem better. This also has a huge benefit that we could alternatively store the private ssh key in Github secrets instead of Azure Key Vault and then use the jsonnet base64 encoding function in a yaml file to sync the Github secret using ArgoCD which makes the overall solution simple!

 

Idea priority Urgent