This is an IBM Automation portal for Cloud Management, Technology Cost Management, Network Automation and AIOps 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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
See this idea on ideas.ibm.com
We are currently integrating IRIA (IBM Rapid Infrastructure Automation) with legacy Cisco ASA devices that only support TLS v1.0. However, IRIA’s default Node.js HTTPS agent uses TLS v1.2, and there is currently no way to configure or downgrade the minimum TLS version used by the integration logic.
This limitation causes the connection to fail due to TLS version mismatches, resulting in errors like unsupported protocol during SSL handshake. While Node.js supports flags such as --tls-min-v1.0 to allow older protocols, there is currently no setting in IRIA to apply this behavior specifically for integrations.
Allow IRIA users to specify the minimum and/or maximum TLS protocol version in the authentication or integration schema. This setting would enable backward compatibility with older network equipment, such as TLS v1.0-only Cisco ASA firewalls.
Idea priority | High |
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.
@Guest TLS1.1 is a version of TLS from 2006 that is deprecated and disallowed by the internet standards and regulatory bodies, as well as vulnerable to multiple attacks. or these reasons, TLS1.1 is end of support in most services from years ago.
By default, TLS1.1 cannot be used in the RIA / Concert Workflows worker at this time.RIA / Concert Workflows will be FedRamp certified in its next release. TLS1.1 is not allowed by FedRamp / FIPS, therefore it is not possible to implement a working solution from the integration side. Migrating containers to UBI will also prevent the use of TLS1.1, which is disabled or removed by default in OpenSSL.
We recommend that the client side upgrade to a supported TLS version.