Skip to Main Content
Integration


This is an IBM Automation portal for Integration 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 Submitted
Workspace App Connect
Created by Guest
Created on Jun 30, 2026

Expose a pre-emptive vs. reactive authorization toggle for Basic Auth / OAuth directly in the security policy

Right now, whether the server challenges a client pre-emptively or reactively for Basic Auth or OAuth comes down to a setting that's hidden. It's not in the security policy where you'd expect it, and the docs don't make it obvious. You only find it if you go looking, and most people don't know it's there.

Make it a proper toggle in the security policy, for both Basic Auth and OAuth.

Reactive: the server answers an unauthenticated request with a 401 and a WWW-Authenticate challenge, and the client resends with credentials. Pre-emptive: the server expects credentials on the first request and doesn't challenge.

The two behave differently enough to matter. Some clients only send credentials after a challenge, others send them up front. Pick the wrong mode and you get 401s with nothing useful to go on, because the setting that controls it isn't anywhere near where you configure security. A documented, per-policy toggle takes the guesswork out.

Idea priority High