Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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 Under review
Created by Guest
Created on Jun 22, 2026

Can the out-of-the-box CustomIVInvokeRestAPI service be altered to meet our requirements?

Current Implementation: We are using internal class `RemoteApplicationOAuth` directly (unsupported approach by IBM) to make calls to SIM & IV via OMoC.

- IBM Recommendation: Migrate to `CustomIVInvokeRestAPI` SDF utility service (supported method) https://www.ibm.com/docs/en/order-management?topic=isipiv-calling-inventory-visibility-apis-through-sdf-utility-service

We attempted to use CustomIVInvokeRestAPI, but upon invocation, we observed that the response and error structures differ from those in the internal class RemoteApplicationOAuth. Due to this discrepancy we need to change our entire architecture, which in turn requires our downstream services to make corresponding adjustments. Since IBM handles both authentication and IV call within a single service, could you provide a separate service specifically for authentication?

What is your industry? Retail
How will this idea be used?

Current Implementation: We are using internal class `RemoteApplicationOAuth` directly (unsupported approach by IBM) to make calls to SIM & IV via OMoC.

- IBM Recommendation: Migrate to `CustomIVInvokeRestAPI` SDF utility service (supported method) https://www.ibm.com/docs/en/order-management?topic=isipiv-calling-inventory-visibility-apis-through-sdf-utility-service

We attempted to use CustomIVInvokeRestAPI, but upon invocation, we observed that the response and error structures differ from those in the internal class RemoteApplicationOAuth. Due to this discrepancy we need to change our entire architecture, which in turn requires our downstream services to make corresponding adjustments. Since IBM handles both authentication and IV call within a single service, could you provide a separate service specifically for authentication?

  • Guest
    Jul 8, 2026

    1. How is auth currently done? >> We are using OBB provided service that calls invoke method com.ibm.sterling.afc.services.utils.RemoteApplicationOAuth

    2. What is the expectation? >> Same as how the existing googInovkeSIMService is working

    4. Do structural response changes matter? >>yes

    5. What's the risk of the service managing and reusing the token? >> Token can be cached but IBM needs to make sure cache token is not expired.

    6. It seems want a service to handle authentication alone, and then you will take care of calling the actual API through customization. Is this understanding correct? >> Correct

    If yes can you consider calling the oauth2/token API also? >> Google recommends to use the token provided IBM framework itself.