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

It should be possible for Control Center to handle multiple SSL/TLS keys in its keystore

Currently can Control Center only work with one unique key in its keystore. When using SEAS authentication this certificate must be defined with both Server and Client Authentication Enhanced Key Usage (EKU).

It should be possible (as any other component of the Sterling Suite (Secure Proxy, B2B Integrator, External Authentication Server)) to be able to define the usage of the different keys in the keystore:

Good examples are the following scripts of other Sterling components:

  • SEAS: SEASCipherConfigTool.sh
  • SSP: configureCmSsl.sh / configureEngineSsl.sh
  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • May 15 2019
  • Needs review
How will this idea be used?
  • Define which key / certificate to be used for the Control Center Web Interface / JAVA GUI (with X509v3 Server Authentication EKU)
  • Define which key / certificate to be used for client authentication with SEAS (with X509v3 Client Authentication EKU) or SI B2Bi CCInterop WS
  • Define which key / certificate to use for Cognos
  • Define which key / certificate to use for Client Authentication on a Connect:Direct node
  • etc
What is your industry? Insurance
What is the idea priority? Urgent
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files