Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform 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

WebSphere Liberty

Showing 70

Add new option to IBM WAS and Liberty to allow customers to configure WAS/Liberty to not close HTTP connections when WAS/Liberty are sending back response where the HTTP response code is greater than 399

We are making heavy use of IBM z/OS Connect and IBM z/OSMF. We have found that when a request fails in zCEE and zOSMF, the underlying Liberty product sends back a HTTP response code greater than 399 and closes the HTTP connection from the client. ...
over 1 year ago in WebSphere Liberty 4 Not under consideration

Clients have requested this capability. It would round out the filesystem consuming controls by giving stdout and stderr the same log filesystem space consumption as messages.log

Clients have requested this capability. It would round out the filesystem consuming controls by giving stdout and stderr the same log filesystem space consumption as messages.log It should be possible to redirect Liberty server's stdout and stderr...
over 1 year ago in WebSphere Liberty 2 Not under consideration

Kill on WLP client command should be propagated downstream

Often JEE application clients are used as a gateway between other applications and Liberty (e.g. transforming a proprietary TCP-based protocol into EJB calls). To start the client the "run" command is being used. When using the "run" command two p...
about 6 years ago in WebSphere Liberty 2 Not under consideration

Support Outbound SSL Filters for wmqJmsClient

In WebSphere Liberty Profile the transportSecurity-Feature provides the possibility to use different key-/truststores for different connections (filters). This works fine for http-protocol, but does not work for wmqJmsClient. For wmqJmsClient alwa...
over 6 years ago in WebSphere Liberty 1 Not under consideration

allow groups search across the base entries in WebSphere Liberty like in WebSphere ND

Many organizations have multiple Active Directory Domains, and sometimes users belong to one domain are being assigned to groups in other domains, currently liberty is able to fetch group associated with user from same domain, it doesn't fetch the...
over 1 year ago in WebSphere Liberty 1 Not under consideration

Microprofile openapi uses the default host

Standard web applications can use virtual hosts in Liberty but feature WABs such as microprofile openapi can not. The requests should be made using the default host name.
over 3 years ago in WebSphere Liberty 2 Not under consideration

Hybrid flow for openidConnectClient and openidLogin

Only implicit flow is available for oidc login. Hybrid flow is believed as more secure
over 1 year ago in WebSphere Liberty 2 Not under consideration

Allow customizations on the Admin Center pages

For Liberty allowing the addition of some text on the screens would allow to differentiate the Admin Centers so makes are not made. This would be similar to tWAS changing the console identity.
over 5 years ago in WebSphere Liberty 1 Not under consideration

Liberty JSR-352: Provide the ability to submit batch jobs under an alternate userid

In the JSR 352 jmsActivationSpec, possibly under the under the messageSelector, allow for the specification of an alternate predetermined userid underwhich the batch application should run under within the executor.
about 8 years ago in WebSphere Liberty 1 Not under consideration

Java HealthCenter fails to start in Liberty via Java Attach API

The issue is that WAS/Liberty uses the OSGi framework, which registers as the InitialContextFactoryBuilder for the NamingManager if the jndi-1.0 feature is in use. This then prevents any code that does not have a BundleContext from registering a n...
about 6 years ago in WebSphere Liberty 1 Not under consideration