IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

IBM Sterling Rest Services should support BASIC and STANDARD authstyles at a time in the same instance

LIMITATION: In IBM Sterling Order Management 9.4 and 9.5, Currently If we want to use Rest Services in one deployment we have to choose either of the one authstyles 'BASIC' or 'STANDARD' only.

Customer has deployed SMCFS on 2 WAS instances to serve all the synchronous requests and wants to use OOTB Rest Apis.
One of the Order capture channels has need to call IBM Sterling synchronously, and with multiple parallel threads, And they dont have need to track any user activity to maintain the tokens, So planned to use BASIC servlet.authstyle.
But there are other scenarios where in customer will have a valid user LoginId/Token then they need to use those credentials to call Rest service instead. Then we need to use STANDARD servlet.authstyle.

Where-in most of the calls use BASIC authstyle way, and few need to use STANDARD authstyle.

Problem, with current Rest Services support is in IBM Sterling we don't have any servlet.authstyle specifying both these features of BASIC and STANDARD authstyle. I was wondering why was this not supported. This is need of the hour.
Please do needful.

  • Guest
  • Mar 20 2018
  • Not under consideration
Order Management (OnPrem & OMoC)
What is your industry? Retail
How will this idea be used?

Provide synchronous REST calls to Order Capture system and To another application which has access to loginId and token. So that we will be able to call IBM Sterling via Rest Service calls REST APis in both modes (authstyles) with the same deployed Enterprise application in WAS.
  • Guest commented
    11 Jun, 2020 12:13am

    This is currently being considered

  • Guest commented
    11 Apr, 2019 07:57am

    "Token information should not be a part of URL. There should be a provision to pass it in header parameter." -- I too agree with this.

  • Guest commented
    7 Jan, 2019 06:06am

    Token information should not be a part of URL. There should be a provision to pass it in header parameter.

  • Guest commented
    16 Aug, 2018 09:55am

    I don't see any update on this. Appreatiate if any one form PRODUCT repsonds on this.

     

    Thanks,

    Sunith Dodda.

  • Guest commented
    27 Jun, 2018 01:00pm

    Strongly recommend

Related ideas

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.