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
Start by posting 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,
Post an idea
Upvote ideas that matter most to you
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 offering manager 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 a 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.
If you encounter any issues accessing the Ideas portal, please send email describing the issue to firstname.lastname@example.org for resolution. For more information about IBM's Ideas program visit ibm.com/ideas.
Using custom apic-ingress-ca certificates for API Manager GUI
We are running API Connect EUS version on CP4I EUS version on Openshift 4.6.21 on Azure cloud.
As part of our internal security requirements, we wish to replace the default cert-manager generated API Manager GUI (https://apic-mgmt-api-manager-apic.cpi.qa.ocp.tine.no/manager/) certificate "apic-ingress-ca" with a custom certificate which is signed by our internal PKI system. The certificate we wish to use already has a CN=*.cpi.qa.ocp.tine.no which is set on Openshift ingress, in other words, when a user is logging in to API Manager, they shouldn't have to trust multiple certificates in order to be allowed in, not to mention the security risk of using a self-signed IBM generated/cert manager generated certificate in the value chain.
We need this feature/functionality on our EUS/long term release of CP4I in case this fixed in a future version of API Connect.
Do not place IBM confidential, company confidential, or personal information into any field.