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 email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
The Useable WebSphere Auditing Functions Are Required by the Department of Defense
The current WAS Auditing function does provide readily useable logs to even track down simple events such as starting/stopping an application server via the WAS Admin Console. I would like to see such functionality added to the NDM audit logs. I a...
I have a updated version of a application that now parts of uses WebSockets. IIS supports WebSockets but not the ISAPI Plugin. I am told that Apache would support this but I dont think this is a option for me. If you bypass IIS and go directly to ...
Add support for com.ibm.mq.cfg.jmqi.useMQCSPauthentication in WAS 8.5.5.X
Currently the MQ RAR packaged with WAS 8.5.5.X is too old to support com.ibm.mq.cfg.jmqi.useMQCSPauthentication. This means that for anyone who is unable to move to WAS 9 any MQ connection is required to use far less secure passwords.
Allow encryption algorithm to be AES-256 in GCM mode for JAX-WS and JAX-RPC security runtime.
We have recently upgraded to AES-256 in CBC mode on JAX-WS and JAX-RPC security runtime for our application servers, however we are required by our cryptography standards to move to the preferred GCM mode before the end of 2021. This option does n...
Create User for WAS Console That can see only Applications tab After login
create user for application team to enable them to deploy their application only, after this newly created user logins cant see or interact with any tabs within WAS console except Applications tab only.All WAS console tabs become invisible to this...
Support java 11 Websphere Express(8.5.5.x)/Base(9.0.5.x) WebEnablement on IBM i
As currently announced by IBM Websphere Express(8.5.5.x)/Base(9.0.5.x) are supported at least until 2030 and there is no EOS announced after 2030. https://www-01.ibm.com/common/ssi/cgi-bin/ssialias?subtype=ca&infotype=an&supplier=897&l...
Allow for multiple Subject Alternative Name DNS entries in Certificate Signing Requests in the WAS admin console
In WebSphere 8.5.5 fix pack 18 support for specifying Subject Alternative Names DND, IP, email values was added when creating a certificate signing request (CSR) via the WebSphere Administrative Console. However, the capability currently allows on...
We have a requirement to update WAS settings from within the secure wsadmin.sh runtime. The updates require calling out to other servers in our network using REST-ful calls. The GitHub "requests" module meets most needs. But we can not use it beca...
Do not place IBM confidential, company confidential, or personal information into any field.