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 for resolution.

For more information about IBM's Ideas program visit

Status Future consideration
Workspace WebSphere Liberty
Created by Guest
Created on Jan 23, 2019

Liberty should support AT-TLS "awareness"

Liberty profile JVMS should support AT-TLS "awareness" at the same level that other products like CICS do.

Idea priority Medium
RFE ID 129243
RFE Product WebSphere Application Server
  • Guest
    Dec 6, 2019

    We are strongly vote for this RFE, because we need ATTLSAWARE for in- and outbound communication in Liberty-Server.

    When we now use AT-TLS on outbound communication, then all applications has to change their URLs from "https" to "http". If they have further SSL-aware parameters in their URL, they have to exclude it. Otherwise Liberty demands a SSL-configuration. What we need is an ATTLSAWARE-Parameter, that applications can use their https-URL, but Liberty checks, that TLS will be done by Comm-Server.
    Now it is really confusing for applications. Use they "http" or "https". And furthermore it's a huge problem, moving applications from local Liberty to CICS-Liberty

    Same procedure for incoming requests. We want to use the httpsPort in the endpoint-definition in server.xml. So, that it is clear, that we run with SSL.

    Best regards,
    Juergen (DATEV eG)