This portal is to open public enhancement requests for IBM Sterling products and services. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updateson them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
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:
SSP: configureCmSsl.sh / configureEngineSsl.sh
What is your industry?
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
Do not place IBM confidential, company confidential, or personal information into any field.