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
When you configure the management console on a Linux host (probably also on Windows) to connect to a launcher, You are required to configure the network connection to the launcher and the username and password to logon.
This configuration is stored on a general location ($DTX_HOME_DIR/mgmtconsole.bin) and will be used by every user who wanted to use the management console on that host.
The action is to prevent users from using the same creditionals!
To resolve this, you must currently install the runtime and monitoring software for each user at a new location and ensure that other users cannot use it. I don't think this is the solution to implement authentication and authorisation.
Can you create a better solution? For example use a webgui, where you have to logon using LDAP(S) for authentication and autorisation.
How will this idea be used?
Our administrators login the management console using a Linux host using a X terminal
|What is your industry?||Government|
|What is the idea priority?||Urgent|
|Link to original RFE|