IBM Sterling Ideas

formerly Watson Supply Chain

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. 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

Passwordless login in CDWS

Our connect-direct node is using a passwordless unix user for communicating with our partners node (snode).

As of right now (v the Connect:Direct WebServices GUI is requiring password in order to login on our node. There seems to be no way of disabling the password input for a certain node, through admin functions.


We wish to not have to add a secondary "gui user" to our OS, just to get the CDWS to work with our setup.

If I recall correctly, the option to disable password on login, was available in the v.1.5 version of the web gui.


I must also say that the new web gui is a huge improvement over the old one, well done!

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Sep 6 2019
  • Declined
How will this idea be used?

It will be a huge improvement to usability in setups like ours, where a passwordless OS user is being used for authentication.

Also it will be a more easy transition from the old 1.5 web gui to the new one.

What is your industry? Financial Markets
What is the idea priority? Medium
  • Attach files
  • Admin
    Chris Sanders commented
    25 Jun 02:04am

    Thank you for opening this enhancement request with IBM. I have reviewed it thoroughly with my team, but unfortunately we will not be able to accept this. One of the benefits of Connect:Direct is that we have very thorough security standards and removing the requirement to authenticate users would conflict with those standards. You could explore the option of using your browser to store credentials for you if you choose to however. That would likely provide most of the same functionality that you've requested. Thank you for opening this enhancement request with us and please don't hesitate to use the tool in the future if you have other ideas we should consider.


    Chris Sanders

    Connect:Direct Offering Manager