IBM Sterling Ideas

Submit new product ideas for IBM Sterling 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.

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.

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

Allow for generic or service accounts that don't expire passwords for systems making calls

Either allow for generic or service accounts with non-expiring passwords or allow for other authentication means for apps that are making calls. Resetting every x days is intrusive.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Aug 3 2018
  • Delivered
How will this idea be used?

A user could integrate an app like Salesforce that makes REST API calls to PEM and issue a  service account that doesn't have an expiring password, so they don't need to reset/change it quarterly.

A user could integrate an app like Salesforce that supports token-based auth or key-based auth and use that rather than a password.

What is your industry? Banking
What is the idea priority? Medium
  • Attach files
  • Avatar40.8f183f721a2c86cd98fddbbe6dc46ec9
    Guest commented
    8 Jul 08:09pm

    PEM calling PEM APIs can now use the internally-generated token authentication, and this is working.

    External system calling PEM as described in the original request, still requires changing the password every 90 days. There is no way to create a service account with a non-expiring password.

    One solution is a randomly generated API key that is only displayed once and functions as a password. Another solution is implementing SSO or LDAP authentication so the internal PEM user database is not used. Both these approaches are used in many large SaaS offerings.

  • Admin
    Greg Russell commented
    22 Feb, 2019 04:21pm

    We intend to address this requirement in an upcoming release.

  • Admin
    Greg Russell commented
    22 Feb, 2019 04:20pm

    We intend to address this requirement by supporting the use of tokens for the API Configurations.  This will allow the primary sponsor administrator to choose to support tokens rather than user name and password.  This will remove the need for the primary sponsor administrator to have to update the passwords on the various API Configurations when they update their login password.