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 Future consideration
Workspace DataPower Gateway
Created by Guest
Created on Apr 17, 2023

Remove RunTime Dependency (For Each Request) on Primary Gateway by OAuth Secured APIs

Customer is having one of the larger DP Gateway clusters deployed to implement their Enterprise API layer.
They’re having single active-active DP GW cluster set up across two sites – each site having 6 GW instances - even distribution such that site failure causes quorum condition to be breached. This is a point installation.

Why Helpful:
 Once the dependency is removed, when one site fails or there is a network partition, OAuth based APIs will still work fine. Not causing outage.

Who Would Benefit:
 Customers:
   who want to achieve active-active across sites thru a single cluster, and
   who have OAuth based APIs deployed to the cluster

How Should It Work:
 Ideally, OAuth APIs should not throw 401 in the failure scenarios (on site down or network partition)

Idea priority High