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.

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.

  • Guest
  • Jun 6 2018
  • Planned for future release
What is your industry? Non-Industry Specific
How will this idea be used?

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

  • Guest commented
    17 Sep, 2020 09:55am

    A SIGNON to C:D Server from PEM via REST API is succesful if using these headers (the value of X-XSRF is fixed and documented on KC, Authorization is Userid/Password in base 64)

    Content-Type=application/JSON; charset=iso-8859-1
    X-XSRF-TOKEN=Y2hlY2tpdA==
    Authorization=Basic ZG5pY2hlOnN0ZXJsaW5n

    PEM is receiving then only the body as an example:

    [ {
    "messageCode" : 200,
    "message" : "Signon is successful",
    "version" : "6.1.0.0",
    "nodeName" : "CDUNIX61"
    } ]

    The header is not captured, but we need these values like:

    XSRF-TOKEN=e00a9b95-a63b-4e32-9f8a-383299e18399

    Authorization : oTqJSyTijkZFyoG4iONdpLeX6n8SSZtegbJVusJSxlPShEEcsibA...

    fur subsequent REST API Calls to the C:D Server otherwise we get an error.

    This can be verified and tested from Postman or other utilities.

    Regards

  • Guest commented
    14 Jan, 2019 01:54pm

    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"}

  • Guest commented
    27 Dec, 2018 07:22am

    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.

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.