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 updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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.
Do not place IBM confidential, company confidential, or personal information into any field.