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.


Add a new idea Subscribe
Status Needs more information
Workspace API Connect
Created by Guest
Created on Jul 31, 2024

RELATED IDEAS

Syncing of Oauth tokens across gateway services in a catalog

If we can sync the Oauth tokens across gateway services, then doing a DR will be seamless and without any downtime. 

We have setup our environment across 2 DCs for high availability. Even if all our APIs deployed in both the DCs we are still unable to route the traffic in both DCs because Oauth tokes are not getting synced. Even during the planned DR activity, we need to have downtime as the Oauth token generated in 1st DC gateways will not be available in 2nd DC. 

Idea priority High
  • Admin
    Dan Temkin
    Reply
    |     Aug 5, 2024

    Thank you for submitting this request. It seems like you are trying to use 2DC for HA and not for DR. If that is correct we would like to remove any statements about DR from the request. If this is for DR please explain why requesting the Application to have to re-authenticate during what should be a rare occurrence of a DR is causing downtime? We do understand that it would cause users to take additional actions but this is not outside the 'bounds' of an OAuth transaction flow so seeing it as downtime or outage is what we are trying to understand.

    For Multi-Region (high latency) deployments what is the out of sync tolerance where the tokens in site A and site B can be different? Is site A always the authoritative source and site be is a read-only replica (aka site B can't perform a token revocation)?

    Also, can you please provide more details if you are using the Token Management with the DataPower API Gateway (https://www.ibm.com/docs/en/api-connect/10.0.8?topic=tokens-token-management-datapower-api-gateway) to determine if that is also in scope.

    This and many more details would be very helpful for designing a solution.

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.