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.


Add a new idea Subscribe
Status Submitted
Workspace API Connect
Created by Guest
Created on Sep 17, 2025

RELATED IDEAS

APIC should use the cert manager generated certificate as the gateway invocation certificate in the Default Client TLS Keystore

Today the certificate in the Default TLS server keystore that is auto-generated by APIC during installation and is valid for 5 years. Its used as the default containerized gateway invocation url certificate. There is no option to extend this and in case its expired, customer need to create a new Keystore and create a new certificate.

Although its not recommended to use the Default TLS Server keystore and the corresping Default TLS server profile which references that keystore by default but many customers are using it especially on containerized gateways in test environemts as its all auto-generated by APIC.

Furthermore there is a certificate generated that is managed by Cert Manager that seems to correspond to this TLS Server keystore  / API Invocation Url certificate but is not used.

The request is to use this Cert Manager managed certificate and link it to the Default TLS server keystore certificate.

Example:
oc get certificates -n apic | grep gateway
apic-gw-gateway                        True    apic-gw-gateway                        2y17d
 

Its issued by the  apic-ingress-issuer and also the DNS Name in it matches the API invocation url of the containerized gateway. All other APIC certificates are managed by Cert Manager and get auto extended but as this gateway certificate is not linked to the secret in the TLS Server Keystore, customers need to change that certificate manually if it expires.

Idea priority Low

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.