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 Not under consideration
Workspace App Connect
Created by Guest
Created on Jul 3, 2014

RELATED IDEAS

Support AT-TLS in Message Broker

While using AT-TLS encryption for simple outgoing and incoming https requests works fine with message broker as described in the following article: http://www.ibm.com/developerworks/websphere/library/techarticles/1003_suarez/1003_suarez.html and in the broker documentation for Version 8.0.0.4: http://www-01.ibm.com/support/knowledgecenter/SSKM8N_8.0.0/com.ibm.etools.mft.doc/bp22770_.htm

Unfortunately this will not work if you want to address a https server though a proxy. The CONNECT string being sent to the proxy must include the https URL. This can only be set by the TargetURL of the HTTPRequestNode. If this is a https URL the broker internal SSL implemetation will be taken. Thus AT-TLS does not work.

I propose the following solution:
Add a "Use AT-TLS" flag to the HTTPRequest Node, that will make the node behave like http no mattter what URL is given. This way the https URL is sent to the proxy and AT-TLS can be used.

Idea priority High
RFE ID 55637
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Reply
    |     Oct 25, 2021

    Idea / RFE Review. Apologies for the length of time this request has been held in the status of Uncommitted Candidate / Future Consideration. Unfortunately due to the very limited proportion of our users wanting to utilize both AT-TLS and also going through a proxy, it is highly unlikely we will prioritize this request from the business viewpoint, so on this occasion we won't be taking this suggestion any further forward.

  • Guest
    Reply
    |     Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

  • Guest
    Reply
    |     Aug 5, 2014

    Thanks for raising this requirement, which I can see would be useful - particularly for our z/OS clients. We'll looking at adding this in a follow-on release.

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.