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,
Post an idea
Upvote ideas that matter most to you
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 firstname.lastname@example.org for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Add a parameter to BBOC START_SRVR commands to define the BBO$ user id for CICS WOLA Link Server Task
We are using BBOC START_SRVR commands to start the WOLA Link Server Tasks (BBO$) in our CICS regions. Currently, there is no parameter to define the user id, under which BBO$ is running. So, if we start the Link Server Task during the CICS startup...
In WAS z/OS traditional cells, we are using the paramters: com.ibm.security.SAF.authorization = false and com.ibm.security.SAF.delegation = false.The developers use the application-bnd.xml files to map J2EE roles to a bind-able referenced role in ...
Provide a feature for Dynamic IP restriction settings for IBM Websphere Liberty server
Our product runs on bundled IBM Liberty Server. The version of the Liberty that gets deployed with the product is “WebSphere Application Server 184.108.40.206/wlp-1.0.31.cl190820190813-1136”.Currently IBM Websphere Liberty does not provide any mechanism...
The use of bells-1.0 makes it easy to develop and deploy a liberty extension, but often it is very wanted to be able to configure the module.Currently the only way is to share environment variables, but the normal Liberty way is to put properties ...
Our product uses the JMS support within Liberty to publish messages that can be subscribed to by clients (Eclipse plug-in or Ant build) to get feedback on long running processes. Currently we rely on the WAS thin client for JMS to provide this cap...
Allow usage of z/OSMF JWT tokens by multiple sessions using the same user ID
We are using new APIs to obtain JWT tokens (/zosmf/services/authenticate) from our automated scripts that use other z/OSMF REST APIs with the obtained. After the script completes, it calls the DELETE method to invalidate the token that it obtained...
Option to configure OIDCClient to pass the sessionID in a more secure manner
We have learned from our security team that the session ID for the /oidcclient/redirect/azureclient URL is being passed in the URL using clear text. I had opened a case with WAS support to see how the issue could be mitigated by sending sessionID...
Administration and application traffic on different ports
For better security, an application server's application traffic can be initiated from the web server in the DMZ, but it should not be possible for administration traffic. For Liberty profile, it is difficult to achieve.