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 Not under consideration
Workspace WebSphere Liberty
Created by Guest
Created on May 12, 2016

Restrict which http method can be called

For better security, it should be possible to configure what http methods can be used to access an application. For example, application 1 may only allow http get/put. Application 2 may disallow http options.

This applies to both traditional WAS and Liberty.

Idea priority High
RFE ID 88310
RFE URL
RFE Product WebSphere Application Server
  • Guest
    Mar 12, 2021

    Thank you for the suggestion. The requirement does have merit, but looking at it with respect to our total backlog of requests we do not see sufficient interest in this enhancement to merit delivery any time in the foreseeable future. Given the unlikelihood that we would deliver this, we are declining the request rather than leaving it in an uncommitted state for an extended period of time. If you would like to discuss this decision further, please contact Graham Charters .

  • Guest
    Jun 15, 2016

    Can't you get the same result by configuring restrictions in web.xml and requiring a role that nobody is in?