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 Future consideration
Workspace App Connect
Created by Guest
Created on Jul 21, 2022

RELATED IDEAS

Make all truststore and keystore elements available in the custom resource - not just HTTP listener / input (ingress)

Currently in the IBM App Connect Custom Resource a keystore and truststore can be specified for the ‘forceHTTPS’ keys and certs. However, this only influences the PKI / TLS setup for the HTTP Listener configuration (fine for the HTTP Input node, doesn't work for the HTTP Request node), many other configurable certificates and keys cannot be allocated at deploy time in the custom resource e.g. JVM keystores / truststores used to establish trust chains for egress e.g. HTTP Request nodes etc Request is to make all truststore and keystore elements available in the custom resource e.g. JVM, ELKConnection available to be added. Additionally, where necessary generate the required file from a key and certificate e.g. the HTTPS: keystoreFile: /myKeystore.p12 rather than having to supply a P12 file.
Idea priority Medium
  • Admin
    Ben Thompson
    Reply
    |     Sep 12, 2022

    Idea / RFE Review. Thank you for taking the time to raise this suggestion, we agree that the wording in the documentation of the property "spec.forceFlowHTTPS.enabled" should be improved to highlight that the parameter only applies to inbound traffic rather than egress (the parameter indicates whether to force all HTTP Input nodes and SOAP Input nodes in all deployed flows, including their usage for inbound connections to Applications, REST APIs and Integration Services, should use TLS). We apologise for this confusion and we'll update the docs at the next earliest available opportunity. Regarding the wider scope of the suggestion we agree that extending support to receive keystore/truststore files rather than the certificate and key files would improve usability, and that it would also be helpful to cover other transports. Status of the suggestion is moved to Future Consideration.

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.