Skip to Main Content
Cloud Platform

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:

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,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. 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 portals, please send email describing the issue to ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Delivered
Created by Guest
Created on Nov 19, 2020

TLS 1.3 support with TLS 1.2 fallback

We need in tWAS 8.5.5 support for TLS 1.3 as well as TLS 1.2 for a fallback option.

Idea priority High
RFE ID 146872
RFE URL
RFE Product WebSphere Application Server
  • Admin
    Gary Picher
    Jul 5, 2022

    Hi Mohammed,

    You can specify a comma-separated list of protocols in the ssl.client.properties file, e.g. com.ibm.ssl.protocol=TLSv1.3,TLSv1.2 . The JDK will attempt to communicate with the higher level of the protocol if the server can support it, otherwise it will fall back on the earlier protocol version.

    If this particular client should only ever communicate with servers that support TLSv1.3, you could simply supply com.ibm.ssl.protocol=TLSv1.3. This will cause the client to only attempt to use TLSv1.3. If the client ever attempted to connect to a server that doesn't support TLSv1.3, the client connection would fail by design, which might help you avoid connecting to a less-secure server / identify a server that needs to be upgraded to support TLSv1.3.

  • Guest
    Jul 4, 2022

    Under profiles properties you also have ssl.client.properties and we normally update the com.ibm.ssl.protocol=<protocol>. So when you define both TLS1.3 and TLS1.2 in custom then what should be updated for this property ? Kindly advise

  • Guest
    Mar 17, 2022
    Glad to hear further on this.
  • Admin
    Gary Picher
    Mar 15, 2022

    This support has been added to WebSphere Application Server 8.5.5.21 and 9.0.5.11. For details on how to configure multiple protocols, see Step 14 on the following page:

    https://www.ibm.com/docs/en/was-nd/8.5.5?topic=sc-creating-ssl-configuration

    For example, you can create a "Custom protocol list" that contains both TLS 1.3 and TLS 1.2, allowing TLS 1.3 communication for clients that support it while also providing the ability to fall back to TLS 1.2 for other clients.

  • Guest
    Mar 11, 2022

    Should be a very high priority as TLS1.3 is now becoming more accepted and competing Application Servers have this current functionality.

  • Guest
    Jan 16, 2022

    Is there anything I could also consider in due consideration to this. I continue to observe the floatation on this inspite of environmental priorities. Didn't realise until this morning, this was moved to Idea Portal from the list of prioritized RFE from previous year.

  • Guest
    Nov 19, 2021

    It is imperative that a multiple JVMs within a WAS cell can use both TLS 1.3 SSL protocol with a 'fallback' capability to TLS 1.2

    the current implementation approach recommended by IBM (as per https://www.ibm.com/support/pages/node/6421519 and https://www.ibm.com/support/pages/node/1077951 ) should enhanced as is it is unusable for a cell with a large number of nodes.

  • Guest
    Oct 14, 2021

    Agreed that backward compatibility is a top priority.

  • Guest
    Aug 4, 2021

    also need on WAS 9.0.

  • Guest
    Nov 22, 2020

    Across all platforms. Thanks, Abhishek

  • Guest
    Nov 22, 2020

    I concur. Thanks. Abhishek Kumar.