Skip to Main Content
Cloud Platform


This is an IBM Automation portal for Cloud Platform products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Not under consideration
Workspace WebSphere Liberty
Created by Guest
Created on Apr 24, 2018

<cors> element should allow circumvention of authorization check for pre-flight request

Original conversation in IBM Cloud Slack workspace at https://ibm-cloud.slack.com/archives/C30NGTBFS/p1523882393000167.

When CORS is turned on and application security is also turned on, the OPTIONS pre-flight can be prohibited by the application security (401 Unauthorized) unless the application has specifically excluded OPTIONS from being secured. This is seemingly in contravention of the CORS specification because there should be no authentication information on the pre-flight request.

It feels like, when CORS is enabled, the pre-flight request should circumvent the application security so that it can return the pre-flight response.

This decision is in the server's domain rather than the application, which may be pre-packaged and unaware of the serving situation it may be in.

Idea priority Medium
RFE ID 119245
RFE URL
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Reply
    |
    Dec 8, 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 <charters@uk.ibm.com>.