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

External User should not add in ICC clasic console when we have configured LDAP to authenticate external users

IBM Control Center authenticates with LDAP if we created external users specifically in ICC classic console though we have configured LDAP with SEAS.

 

The Feature Should be as below:

1.) ICC should validate if the user is local or external. If user is not present in ICC classic console, ICC should look the user in LDAP using SEAS and it should not be a mandatory field at ICC classic console to reach SEAS to validate user at LDAP.

 

Present available feature and not a good feature at ICC:

Though we have configured LDAP using SEAS, still we have to manually create no. of users who needs access to ICC web console. This feature is making no point of configuring LDAP to ICC.

 

 

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • Oct 2 2019
  • Needs review
How will this idea be used?

This idea would definitely help to avoid dependency in creation of users specifically though we have configured LDAP to authenticate external users.

This idea definitely gives a point in order not to create users again explicitly at ICC console.

What is your industry? Banking
What is the idea priority? Urgent
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files