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 ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Future consideration
Created by Guest
Created on Jun 3, 2021

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 not appear in the drop down list when selecting Data Encryption Algorithm in the JAX-RPC Default Generator Bindings Application servers > application_server_name > JAX-WS and JAX-RPC security runtime > Encryption information > gen_encinfo or JAX-RPC Default Consumer Bindings Application servers > application_server_name > JAX-WS and JAX-RPC security runtime > Encryption information > con_encinfo .

Idea priority High
  • Guest
    Aug 19, 2021

    We are using version 8.5.5.x. There are options for AES-256 in CBC mode, however we are required to have AES-256 in GCM mode.

  • Admin
    Graham Charters
    Aug 18, 2021

    Thank you for the suggestion. We've not heard back from you in some time, and according to our policy (https://www.ibm.com/support/pages/node/6242260) for reviewing and addressing RFEs we have decided to close this request. If you would like to discuss this decision further, please contact Graham Charters <charters@uk.ibm.com>.

  • Guest
    Jun 8, 2021

    All the new versions of WebSphere traditional allow you to select AES-256 as the Data encryption algorithm (http://www.w3.org/2001/04/xmlenc#aes256-cbc). Which version of WebSphere traditional are you using which does not allow to select AES-256 Data encryption algorithm?