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 9, 2015

WS-Security policy set bindings don't work with Web SSO global security

State Farm secures all their web resources in their WAR modules, so nothing is left unsecured. We have a JAX-WS web service endpoint. This is also apparently secured by the Web module security. We have WS-Security specific policy sets defined on the JAX-WS Web service endpoint but they never get invoked as global security gets executed first. We have web Single sign-on and web security settings on the application server which always intercept the incoming SOAP requests over http. We will never execute the WS-Security settings on the jax-ws endpoint with global security enabled and our web resources protected with security constraints. We think this is a flaw and there should be a bypass global security/web security mechanism for jax-ws endpoints that have specific ws-security policy set bindings.

Idea priority High
RFE ID 72515
RFE URL
RFE Product WebSphere Application Server
  • Guest
    Sep 25, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Application Platform
    Product - WebSphere Application Server

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Application Servers
    Product - WebSphere Application Server