Watson Supply Chain Ideas

Submit new product ideas for Watson Supply Chain solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

Submit ideas for other Watson Customer Engagement Products:

Watson Marketing
Watson Campaign Automation
Watson Commerce

Support for token authentication

Some of REST APIs for IBM products have token authentication implemented. I.e., call a sign in API to get a token, and then use the token in a HTTP Header for all other API calls.

Example Products:

IBM Sterling Secure Proxy: https://www.ibm.com/support/knowledgecenter/en/SS6PNW_3.4.3/com.ibm.help.ssp.apis.doc/CommonFiles/rest_api_request_headers.html

IBM Connect Direct: https://www.ibm.com/support/knowledgecenter/en/SS4PJT_5.3.0/cd_webservices/cd_webservices_restfulapi/authenticating_rest.html

PEM currently does not support this form of authentication in API configuration and API dialogs.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Jun 6 2018
  • Uncommitted Candidate
How will this idea be used?

This will be used to call REST APIs of IBM SSP and CD products from PEM.

What is your industry? Non-Industry Specific
What is the idea priority? Medium
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    December 27, 2018 07:22

    Please consider as well to provide:

    • an out of the box activity for SSP and C:D use cases for PEM and PP
    • enhance the partner repository  and modify the SSP and C:D configurations.
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    14 Jan 13:54

    For full Connect:Direct support tokenization will not be enough. You will need to enable as well numbers in json documents instead of only text. Following an example:

    This is how the C:D signon json should look like:

    {"ipAddress":"127.0.0.1","port":1363,"protocol":"tcpip"}

    In PEM you can do this if port number is hard coded. Anyway if you gathered the port number in the PEM activity at some point in time and now want to reuse the number PEM can only generate the number as text. See following the example:

    {"ipAddress":"127.0.0.1","port":"1363","protocol":"tcpip"}

    Stating the port as text instead of number fails the C:D signon.

    PEMs missing support for number stating in json documents effects not only the C:D signon but as well other C:D APIs where number are needed instead of text.

    Just to make it clear. PEM prevents saving API calls like this:

    {"ipAddress":"127.0.0.1","port":${/Parameters/ActivityContext/Task[@Name="GetPandSnodeInfo"]/Dialog[@Name="GetCDPnodeInfo"]/Response/ObjectNode/apiport/text()},"protocol":"tcpip"}

    You can only save it as follows which is by stating a number as text in the json document:

    {"ipAddress":"127.0.0.1","port":"${/Parameters/ActivityContext/Task[@Name="GetPandSnodeInfo"]/Dialog[@Name="GetCDPnodeInfo"]/Response/ObjectNode/apiport/text()}","protocol":"tcpip"}