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.
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 bec...
Support Java 2 Security to restrict application acceess to local resoures
This a CAT-I finding for DoD STIG: Below is their reasoning:Rule Title: The WebSphere Application Server Java 2 security must be enabled.Discussion: Java 2 security provides a policy-based fine grained access control mechanism that increases ove...
TLSv1.3 support for IBM WebSphere Application Server
TLSv1.3 support for IBM WebSphere Application ServerPlease enable support of TLS 1.3 for WAS version 855 and 9.RFC standard has been released. The Transport Layer Security (TLS) Protocol Version 1.3https://www.rfc-editor.org/rfc/rfc8446.txtFábio
VET Change Websphere security configuration to allow non-Security Admin managers to generate heapdump/javacore/core files
Websphere 8.0 introduced new functionality that allows administrators to generate heapdumps/system dump/java cores on demand.This is very useful for administrators investigating particular problem types.The default Websphere configuration means th...
Automatically propagate SAF identity when client and server are in the same cluster
For z/OS, customers are always logged into the traditional environments. This means they have an identity that is verified and trustable. The z/OS TCP/IP stack and the Java runtime support the notion of trusted identity propagation. The client ...
Support JDBC 4.2 in WebSphere Application Server 8.5.5
WebSphere Application Server 8.5.5 supports Java SE 8. It should support JDBC 4.2 in accordance with specification of JSE 8 (https://jcp.org/en/jsr/detail?id=337). However, the latest system requirement of WAS 8.5.5 only states support of JDBC up ...
Allow the output repositories to be a zip file in the IBM Packaging Utility
You can not build zip repositories in the packaging utility command line (pucl) in the -target option.IBM support informed that building of taget repositories are not supported.Usually you need zip repositories so after the pucl command line ...
Support for the SAN attribute in the CSR request when using wsadmin or the WAS admin console.
We want to be able to use the SAN attribute in PKI keys/certificates. This is needed to pass host verification during the TLS handshake if the certificate is to be used by processes on different hosts, e.g., multiple WAS application server proces...
Do not place IBM confidential, company confidential, or personal information into any field.